set implementation shouldn't imply -u

[mjrosenb@…]

pmerge -s foo should intuitively be the same as cat /etc/portage/sets/foo | xargs pmerge

however, they don't. with pmerge -s only packages that can be upgraded are listed. I would imagine that the -u flag is to filter out packages that aren't being upgraded, so having this as the default functionality of pkgcore should be considered broken

[patrick.borjesson@…]

While i cannot say anything about the implementation itself, i would guess pkgcore emulates the way emerge handles the 'system' and 'world' sets in portage. Default behavior of emerge regarding these sets is to not reinstall already installed packages unless you explicitly tell it to (with --newuse or --emptytree, or any other relevant flag)

[anonymous]

There was actually a discussion about the handling of sets in portage on the portage-dev mailinglist a while back: http://article.gmane.org/gmane.linux.gentoo.portage.devel/2557

[ferringb]

Take the discussion of this to the ml please; I *personally* lean towards dropping the special behaviour that world/system imply, but that's me.

[masterdriverz]

Perhaps we could make this the case when we go to .5