On Mon, 10 Jul 2017 19:22:47 -0400 "William L. Thomson Jr." <wlt...@o-sinc.com> wrote: > > That part does not require it to resolve deps. Just check world file, > assuming its correct. Though could be thrown off if say gcc, or > another was in the world file. I think the profile or set would catch > that as it does now and generate a warning, regardless.
Speaking of gcc in the world file. I think portage should STOP adding packages that are in the profile or a dep to world. If you merge a package as part of a set, I am pretty sure it does not get recorded to world, need to confirm, could be wrong. A rule for portage could be; - If the package is not in world and already installed. Do not add the package to world. If you are re-emerging a package already installed. You do not have to use the -1 option. I have polluted so many world files with system packages and/or dependencies I re-emerged directly without -1. Those IMHO should never have been recorded to that file. They were brought in by other things. Only things in my world should be packages merged directly, not from profile, set, or a dep. I will file a bug on that as well. -- William L. Thomson Jr.
pgppvJ2qYUHfP.pgp
Description: OpenPGP digital signature
