On Wed, Mar 28, 2012 at 05:43:00PM +0100, Penguin Lover David W Noon squawked: > In that case, the source of the breakage is almost certainly Portage. > > If a slotted package is in the world file without a slot specification, > Portage should really take that to mean "all installed slots are > required" rather than "any slot will do" -- or, worse still, ignore the > world entry and fall back to package dependencies.
I disagree. Portage has always been very clear about this: atoms without slot or version specification means precisely **any slot/version will do**. The behaviour is entirely consistent between the command line, ebuilds, the world and set files, as well as other things in the profile (per package use flag and keyword specifications). W
