-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/17/2013 09:05 PM, Ciaran McCreesh wrote:
> 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.
>
So why is this allowed in this ebuild again?
> SLOT=$(usex multislot "${PV}" "2.5")
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSSWUtAAoJEFpvPKfnPDWzFC4H/2Qif+q8g64TJn4oIoKoTsy4
HBelOIQy6673EbWn5Gq1cdUT7+BCbw5Dj5L1CGcdOLf7bdvklIAPa0w7foSj3rDv
KUzyTb7Vog+KWKgXrmZat/r4u9tN2V/2zdJkKcxQtJnT0Drb3ISo8J4SSK2DBhDH
f1o/FarT5W33bTjwp2BxIksB0sQsp8XsR+hBViMCc7EUJvROEgJO4Cg5lcArALg0
UUoH7T9mmLtNPomB8T4mAKt4aknW+ECeK4TNjsZMr/3JAawgus0YzDx5cz5weJ+J
zQ9YQlMu4USuCYJylf+pWp7OMHtSmKvtrHdtUDv1GNIumXgU3EK0z/2Mj57xJrA=
=XtgG
-----END PGP SIGNATURE-----
