On 08/12/2017 04:39 AM, Paweł Hajdan, Jr. wrote: >> >> The option is the same as --newuse except it ignores functionality that >> you suggest to remove. You could certainly deprecate one option or the >> other if they became the same. But the core functionality of >> system-wide USE changes (by profile or user), needs to be scanned somehow. > > +1 > > There are use-cases for --changed-use / --newuse other than changed IUSE. > > I find it useful to easily rebuild affected packages when changing USE > flags in make.conf. If the flags were removed, would we have a good > alternative? >
I simply overlooked the global USE change in make.conf because IMO it's a nonsense operation. But people do it, and we support it, so for the sake of argument forget I mentioned removing --newuse. The --changed-use flag would be redundant, though (it would do the same thing as --newuse).
