On Thu, 4 Feb 2016 13:01:25 +0100 Dirkjan Ochtman <d...@gentoo.org> wrote:
> On Thu, Feb 4, 2016 at 11:27 AM, Jason Zaman <perfin...@gentoo.org> wrote: > > Which looks easier and nicer to you? > > > > NGINX_MODULES_HTTP="access auth_basic autoindex browser charset > > fancyindex fastcgi geo gzip limit_req limit_zone map memcached proxy > > realip referer rewrite scgi spdy split_clients ssi upstream_check > > upstream_ip_hash userid uwsgi" Well, the real issue here is that people are using USE_EXPAND as some kind of 'here, upstream give us some grouped options, let's thoughtlessly expose them all in some fancy USE_EXPAND without thinking about usability of the solution!' Of course, some of those flags make sense as USE flags. Some don't. There are things that you practically always will want enabled. There are things that should be controlled by global USE flags but instead land in some custom USE_EXPAND because... because we can group it with 15 mildly relevant options! So I have USE=zlib enabled because I want gzip support. But no, for nginx I have to look through USE descriptions and find it's actually nginx_modules_http_gzip because it happens that it is realized using a loadable module! -- Best regards, Michał Górny <http://dev.gentoo.org/~mgorny/>
pgpMZYBseAeCp.pgp
Description: OpenPGP digital signature
