On Fri, Feb 12, 2016 at 1:36 AM, Kent Fredric <kentfred...@gmail.com> wrote: > On 12 February 2016 at 18:56, Duncan <1i5t5.dun...@cox.net> wrote: >> So my USE="-* ..." (without letting portage do autounmasking) would >> continue to work just like it does now, correct? > > I would hope so.
That would be my proposal. > And obviously, this feature would be potentially > tenous, and might be wise to only > activate its mechanics with a parameter to emerge. >,,, > That way, people who do want the new behaviour can stick it in the > default emerge options and \o/ Whether you call it a FEATURE or an option it would almost certainly have to be defaulted. If you run with that option for six months and then run emerge without that option while using something like --newuse, it will immediately detect a bazillion dependency conflicts and if using autounmask it will want to add 1000 lines to your package.use - which would be the same 1000 lines that many are running with today. I think it would make more sense in general for this to be the default and to have a flag to disable it, in part for this reason. It wouldn't affect people running -* and such anyway, so this is targeted mostly at users who don't care a great deal about micromanaging their USE flags. -- Rich
