| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 12/05/14 23:16, Brian Dolbec wrote: |
| 5 |
> Well, that is debatable, but, it's been reported as being in |
| 6 |
> portage on that eapi bug now. So at the very least you need to |
| 7 |
> wrap it in something that checks eapi or the portage-3 format, |
| 8 |
> Something that is not yet clear to me which. And instead of |
| 9 |
> tracebacking like it did, have it error out instead. |
| 10 |
I'll look into it soon. |
| 11 |
|
| 12 |
> FIX IT! |
| 13 |
I'm not convinced screaming at volunteers is a good motivational strategy. |
| 14 |
- -- |
| 15 |
Alexander |
| 16 |
bernalex@g.o |
| 17 |
https://secure.plaimi.net/~alexander |
| 18 |
-----BEGIN PGP SIGNATURE----- |
| 19 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 20 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 21 |
|
| 22 |
iF4EAREIAAYFAlNxPBgACgkQRtClrXBQc7XNhgEAi8L45Kk1Elvm31GH4HYL/LkD |
| 23 |
H8AAbmW/GY8hDoTweuoBAKL6iv0dw9/S4pu+CrS2P5w/vTK/2m78x3/cadRLnQsU |
| 24 |
=J+GM |
| 25 |
-----END PGP SIGNATURE----- |
Archives