| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 04/17/2013 09:05 PM, Ciaran McCreesh wrote: |
| 5 |
> On Wed, 17 Apr 2013 14:58:20 -0400 Michael Mol <mikemol@×××××.com> |
| 6 |
> wrote: |
| 7 |
>> On 4/17/2013 2:48 PM, Ciaran McCreesh wrote: |
| 8 |
>>> On Wed, 17 Apr 2013 14:33:29 -0400 Mike Frysinger |
| 9 |
>>> <vapier@g.o> wrote: |
| 10 |
>>>> but i'm super lazy, so even this manual step is annoying. as |
| 11 |
>>>> such, i've added USE=multislot support to autoconf (just like |
| 12 |
>>>> it is with binutils & gcc). |
| 13 |
>>> |
| 14 |
>>> But it's massively illegal and doesn't work correctly in |
| 15 |
>>> Portage. |
| 16 |
>>> |
| 17 |
>> |
| 18 |
>> For the benefit of those of us (well, me) not sufficiently versed |
| 19 |
>> in PMS et al to be able to immediately deduce why it's illegal |
| 20 |
>> and why it wouldn't work correctly in Portage, could you please |
| 21 |
>> elucidate? |
| 22 |
> |
| 23 |
> Metadata variables, such as SLOT, are cached and are required to |
| 24 |
> be invariant. When an ebuild violates that requirement, the |
| 25 |
> package mangler usually sees the wrong value for the variable when |
| 26 |
> doing the resolution. This means the package mangler could |
| 27 |
> calculate and display an invalid resolution for what it ends up |
| 28 |
> doing, or it could ignore the ebuild's attempts at changing SLOT |
| 29 |
> from what the cache holds, or it could do something even worse. |
| 30 |
> |
| 31 |
|
| 32 |
So why is this allowed in this ebuild again? |
| 33 |
|
| 34 |
> SLOT=$(usex multislot "${PV}" "2.5") |
| 35 |
-----BEGIN PGP SIGNATURE----- |
| 36 |
Version: GnuPG v2.0.20 (GNU/Linux) |
| 37 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 38 |
|
| 39 |
iQEcBAEBAgAGBQJSSWUtAAoJEFpvPKfnPDWzFC4H/2Qif+q8g64TJn4oIoKoTsy4 |
| 40 |
HBelOIQy6673EbWn5Gq1cdUT7+BCbw5Dj5L1CGcdOLf7bdvklIAPa0w7foSj3rDv |
| 41 |
KUzyTb7Vog+KWKgXrmZat/r4u9tN2V/2zdJkKcxQtJnT0Drb3ISo8J4SSK2DBhDH |
| 42 |
f1o/FarT5W33bTjwp2BxIksB0sQsp8XsR+hBViMCc7EUJvROEgJO4Cg5lcArALg0 |
| 43 |
UUoH7T9mmLtNPomB8T4mAKt4aknW+ECeK4TNjsZMr/3JAawgus0YzDx5cz5weJ+J |
| 44 |
zQ9YQlMu4USuCYJylf+pWp7OMHtSmKvtrHdtUDv1GNIumXgU3EK0z/2Mj57xJrA= |
| 45 |
=XtgG |
| 46 |
-----END PGP SIGNATURE----- |
Archives