If I make 'emerge -uDNav @system @world' system set is saved to list of world sets effectively going back to old behaviour and destroying new benefits. '-1' flag can be added to go around this, but this breaks old behaviour where '-1' was not needed to update system. System should not be normally allowed in world sets, unless someone specifically sets portage to old behaviour. Reproducible: Always
Many people *want* to add @system to @world in order to get the old behavior. If you don't like it, use -1 when updating system. It does not "break" (change != broken) any old behavior, like you seem to imply.
As said, this is intentional. You can add the following to /etc/portage/sets.conf to avoid @system being added to @world permanently: [system] world-candidate = False
(In reply to comment #2) > As said, this is intentional. You can add the following to > /etc/portage/sets.conf to avoid @system being added to @world permanently: > > [system] > world-candidate = False > So this feature exists already. Could me more broadly known though. Thanks.
(In reply to comment #3) > > [system] > > world-candidate = False > > > > So this feature exists already. Could me more broadly known though. > Thanks. > We discussed this on irc and now we are going to make this the default since, on upgrade, the portage ebuild will automatically add @system to world_sets therefore it should no longer be necessary to add it world_sets via the command line.
This is fixed in 2.2_rc10.
