| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 08/06/12 03:23 PM, Pacho Ramos wrote: |
| 5 |
> El vie, 08-06-2012 a las 12:16 -0700, Zac Medico escribió: |
| 6 |
>> It's close enough to ABI_SLOT that it would make more sense just |
| 7 |
>> to use ABI_SLOT because it's more flexible. |
| 8 |
> |
| 9 |
> In that case, I think it's clear we need ABI_SLOT ;) The problem is |
| 10 |
> how to document it in a way people agree with including it for |
| 11 |
> eapi5 :| |
| 12 |
|
| 13 |
If there's too much resistance it could wait for EAPI=6 couldn't it? |
| 14 |
Essentially we'd all just agree that these issues, which ABI_SLOT will |
| 15 |
be needed to effectively resolve, will have to wait and we shouldn't |
| 16 |
do vast tree-wide workarounds like SLOT every library in existence and |
| 17 |
require all consumers to have ':=' slot operators on their deps. |
| 18 |
|
| 19 |
-----BEGIN PGP SIGNATURE----- |
| 20 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 21 |
|
| 22 |
iF4EAREIAAYFAk/SUwwACgkQ2ugaI38ACPCWtQEArkrEsVYa7/tJ8UT1pDBhDhsJ |
| 23 |
+jdMEsbJa++3bWat9TUA/1YoEaOp3cGShNDraFv+cLQl2Qf+hpz3K1AasJVstQwa |
| 24 |
=Nqw/ |
| 25 |
-----END PGP SIGNATURE----- |
Archives