On Thu, Feb 04, 2016 at 11:03:27AM +0100, Dirkjan Ochtman wrote: > On Wed, Feb 3, 2016 at 11:48 PM, Michał Górny <mgo...@gentoo.org> wrote: > > Could we please finally stop introducing global USE flags that are > > going to only be used by a single package? make.conf already looks like > > random mix of randoms these days, with some extra random cruft being > > added every second Tuesday. > > This is an interesting point, which I hadn't thought much about. > > It seems USE_EXPAND is really popular. What does it bring that has all > these advantages over normal USE flags? It seems like APACHE2_MPMS, > APACHE2_MODULES and CURL_SSL could just be normal USE flags with some > REQUIRED_USE stuff. > > Actually, I'm not really sure I understand why we can't use normal USE > flags for CPU_FLAGS_X86 or PYTHON_TARGETS, either.
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" or: www-servers/nginx nginx_modules_http_access nginx_modules_http_auth_basic nginx_modules_http_autoindex nginx_modules_http_browser nginx_modules_http_charset nginx_modules_http_fancyindex nginx_modules_http_fastcgi nginx_modules_http_geo nginx_modules_http_gzip nginx_modules_http_limit_req nginx_modules_http_limit_zone nginx_modules_http_map nginx_modules_http_memcached nginx_modules_http_proxy nginx_modules_http_realip nginx_modules_http_referer nginx_modules_http_rewrite nginx_modules_http_scgi nginx_modules_http_spdy nginx_modules_http_split_clients nginx_modules_http_ssi nginx_modules_http_upstream_check nginx_modules_http_upstream_ip_hash nginx_modules_http_userid nginx_modules_http_uwsgi What is the problem with global flags? Its namespaced and never going to interfere with other packages. The only difference is the descriptions are in use.desc instead of use.local.desc, why does that matter? -- Jason
