Packages in (custom) sets cannot be reinstalled

[sputnick@…]

One (probably) common use-case for custom sets are collections of live ebuilds that should be upgraded together. Since pkgcore does not allow automatic upgrades of live ebuilds (yet? I hope! :)), the easiest way is to put those ebuilds in a set and upgrade the set. Only that pkgcore does not support this, because it does not re-install the packages contained in the set...

What is needed is either an option to force reinstalling the components of a package set, or do this by default. Portage does the latter, reinstalling the packages of a set when doing emerge @sets/my-set.

[ferringb]

Yeah, an option here would be useful. add an explicit --replace, or --force-replace perhaps?

Having to use such an option for sets is a bit annoying, and indicative the situation needs re-evaluation (or that portage needs a wedgie for treating sets differently ;)

[masterdriverz]

Funny that we went from default behaviour being --replace, and having a --noreplace option, to vice versa, and now we need a --force-replace option. Maybe we should go back to how it was (defaulting to --replace) (at 0.5 probably), and then this ticket could be closed.