On Thu, 29 Mar 2012 11:33:50 +0200, Willie WY Wong wrote about Re: [gentoo-user] Anyone Else "Ping-Ponging" with fltk?:
> 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**. In that case, it is a design flaw in Portage. > 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). When I set a flag in package.use without a version specification, it applies to *all* versions of that package that support that use flag. I have been doing this for quite some years for several slotted packages, e.g. wxWidgets. When I manually stabilize a package in package.accept_keywords without a version specification, *all* unmasked versions of that package become stable. I do this for only one package: paludis. -- Regards, Dave [RLU #314465] ====================================================================== [email protected] (David W Noon) ======================================================================
signature.asc
Description: PGP signature
