I am not sure if that is bug or feature, but see scenario. I have GCC installed: nunik ~ # gcc-config -l [1] x86_64-pc-linux-gnu-5.4.0 * [2] x86_64-pc-linux-gnu-7.2.0 Note 5.4.0 is marked as to be used. Now after update of world when I do emerge --depclean, portage will remove GCC selected as to be used without issue: sys-devel/gcc selected: 5.4.0-r3 protected: none omitted: 7.2.0 Is this correct behavior, shouldn't be there warning to the user: Hey, we will remove your favorite package, are you ok with this?
(In reply to Ladislav Jech from comment #0) > I am not sure if that is bug or feature, but see scenario. > > I have GCC installed: > nunik ~ # gcc-config -l > [1] x86_64-pc-linux-gnu-5.4.0 * > [2] x86_64-pc-linux-gnu-7.2.0 > > Note 5.4.0 is marked as to be used. > > Now after update of world when I do emerge --depclean, portage will remove > GCC selected as to be used without issue: > sys-devel/gcc > selected: 5.4.0-r3 > protected: none > omitted: 7.2.0 > > Is this correct behavior, shouldn't be there warning to the user: Hey, we > will remove your favorite package, are you ok with this? Portage does not look at tools from eselect, gcc-config, etc. If a user wishes to hold a certain slot of a package, they should run, eg., 'emerge --noreplace sys-devel/gcc:5.4.0' to have it added to the world file so it will not be depcleaned.
