On Tue, 9 Feb 2016 12:22:51 +1300 Kent Fredric <kentfred...@gmail.com> wrote:
> The only way you could make that scheme better is having an early > stage in NGINX that shows which module are going to be built /based > on/ the USE flag combinations, and then something with savedconfig > could potentially bar building certain modules. > > > Dependency control : USE flags representing the dep > > Feature control: SavedConfig > > And then the "Feature control" could be tightened up/managed with USE > flags used more sparingly when things depended on them. > That might be useful, if the maintainer is willing to implement it. :) > The biggest downside of this is the disconnect for a user between > "What I want" and "What do I have to select to get what I want" ( For > instance, USE=pcre turning on rewrite support is weird , > Sure, that's why I said these two (image_filter and rewrite) were less obvious. I agree it'd be better to use a local 'rewrite' USE for the rewrite module. > While mgorny is more focused on "Why do I have this dependency" not > "What feature do I want" > > And this of course does nothing for us in regards to the large > collection of USE controlled SRC_URIs ..... > Yes, but we have those in other ebuilds, too, most of which don't use USE_EXPAND. And this thread is supposed to be about the usage of USE_EXPAND in nginx, right? > Because NGINX is monolithic, but its sources are aggregated from a > bunch of different authors for some fun reason, sort of like having a > `linux-kernel` ebuild with a SRC_URI for every single vendor name ( > *barf* ) > > I really do not envy the nginx maintainer. > Me neither. @mrueg or whoever's the maintainer: Thanks for sparing the rest of us from this insanity. :) Regards, Luis Ressel
