| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
I'd thought that the new eclass was designed to ensure that if you asked |
| 5 |
for USE="python" it was built for as many different python ABIs as was |
| 6 |
installed on your system (so python2 and python3 if they're both |
| 7 |
installed). I believe it's possible to ask the eclass which ABIs are |
| 8 |
installed, and ask for the either in-use or highest versions of those. |
| 9 |
|
| 10 |
If they're not mutually exclusive, and if vim won't break if they go |
| 11 |
away, then why should the user choose which ones to enable and disable? |
| 12 |
Why not just get them to say whether they want python support or not, |
| 13 |
and try to accomodate them for as many python versions as |
| 14 |
installed/possible. |
| 15 |
|
| 16 |
I realize there may be some controversy surrounding the new python |
| 17 |
eclass, however that does seem to be how most python packages work these |
| 18 |
days, so I'd say it's better to keep everything working the same way. |
| 19 |
|
| 20 |
Mike 5:) |
| 21 |
-----BEGIN PGP SIGNATURE----- |
| 22 |
Version: GnuPG v2.0.16 (GNU/Linux) |
| 23 |
|
| 24 |
iEYEARECAAYFAkxuRQEACgkQu7rWomwgFXrpJQCgiMBnn9bWdbwtE4xcFsNmmKkV |
| 25 |
IV0An3FC4w3eImueLxZ7bwC3tLkv8+YC |
| 26 |
=uCL+ |
| 27 |
-----END PGP SIGNATURE----- |
Archives