On Wed, 17 Apr 2013 14:58:20 -0400 Michael Mol <mike...@gmail.com> wrote: > On 4/17/2013 2:48 PM, Ciaran McCreesh wrote: > > On Wed, 17 Apr 2013 14:33:29 -0400 > > Mike Frysinger <vap...@gentoo.org> wrote: > >> but i'm super lazy, so even this manual step is annoying. as such, > >> i've added USE=multislot support to autoconf (just like it is with > >> binutils & gcc). > > > > But it's massively illegal and doesn't work correctly in Portage. > > > > For the benefit of those of us (well, me) not sufficiently versed in > PMS et al to be able to immediately deduce why it's illegal and why it > wouldn't work correctly in Portage, could you please elucidate?
Metadata variables, such as SLOT, are cached and are required to be invariant. When an ebuild violates that requirement, the package mangler usually sees the wrong value for the variable when doing the resolution. This means the package mangler could calculate and display an invalid resolution for what it ends up doing, or it could ignore the ebuild's attempts at changing SLOT from what the cache holds, or it could do something even worse. -- Ciaran McCreesh
signature.asc
Description: PGP signature
