On 08/11/2017 07:50 PM, Michael Orlitzky wrote: > == New revisions for USE flag changes == > > I suggest that in hindsight, we can do better. Suppose we require a new > revision for every change to IUSE. Then, > > * We can delete all of the PM code for --changed-use and --newuse and > friends. > > * The documentation becomes much simpler: revbump if IUSE changes. > > * Users can omit --newuse and --changed-use from their lives. > > * All package managers now handle IUSE changes properly. > > * emerge runs a bit faster. > > This has none of the downsides of the current approach. Of course, it > lacks that one benefit -- that you don't have to rename the ebuild when > you change IUSE. Now I'll try to convince you that the rename and > associated rebuilds aren't that big of a deal.
I disagree about removing --newuse and --changed-use from portage. This is not their only use. If you happen to change the effective use system wide, USE= in make.conf for portage, these options scan the entire system for such changes. i.e. 'emerge --changed-use --deep @world' Brian
signature.asc
Description: OpenPGP digital signature
