I have created a new ebuild for nginx which moves module selection from a few use flags covering a small number of the modules, to a use flag expansion covering all the modules available in the present build. This allows user to customize an nginx build to the same extent installing it manually would provide them. I believe this method is similar to how apache base modules are handled so it seems appropriate. Reproducible: Always Steps to Reproduce: 1. The line USE_EXPAND="${USE_EXPAND} NGINX_MODULES" must be in /etc/make.conf 2. To customise the module selection NGINX_MODULES="<list of modules>" goes in /etc/make.conf
Created attachment 218157 [details, diff] patch against nginx-0.7.64-r3.ebuild
Created attachment 218159 [details] the ebuild
Created attachment 218163 [details] ebuild with support for third party modules, passenger
can you please add your CFLAGS patch for passenger?
Created attachment 221529 [details, diff] patch to make passenger respect portage CFLAGs As requested.
thanks, i've added the patch to my nginx ebuild. i have refactored the nginx ebuild for USE_EXPAND too, before i found this bug report, but it looks quite similar to your solutiond and i have adapted a bunch of things, thanks :) see http://git.xnull.de/gitweb/?p=overlay.git;a=blob;f=www-servers/nginx/nginx-0.8.33.ebuild
hollow: would you like to take over nginx maintenance? I don't actually use it, I just maintain it because no one else was.
Created attachment 222029 [details] nginx 0.7.65 with portage, and "modular" configuration base setup. Sorry for the tarball, but this would get messy very fast as there are quite a few files. I've attached the ebuild and related files i'm currently using, which includes the starting of php hosting "support" using fastcgi, although the ebuild does not use it yet. The main interest for me in this version is that it creates a "default" website if there is not one already, and uses sites.d and modules.d folders to do vhosting and support the multiple available configuration options now available. It also turns down the dial a little bit on the passenger and nginx's resource usage, which I think is probabally a good idea for "default" installs.
(In reply to comment #7) > hollow: would you like to take over nginx maintenance? > > I don't actually use it, I just maintain it because no one else was. yep, i can maintain nginx, a bunch of my customers start using it now, so i have to work on it anyway. i have already updated metadata.xml and will go through the other bugs during the next days. thanks
please give 0.8.34-r1 a try, thanks
