| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 29/09/12 11:45 AM, hasufell wrote: |
| 5 |
> On 09/29/2012 05:37 PM, Ian Stakenvicius wrote: |
| 6 |
> |
| 7 |
>> There isn't so much a problem with the current |
| 8 |
>> python-distutils-ng eclass but rather it's to expand it to a more |
| 9 |
>> comprehensive replacement for both distutils and python eclasses. |
| 10 |
>> In order to do that efficiently, most of the core functionality |
| 11 |
>> should be moved so that the new distutils is more like a wrapper |
| 12 |
>> to the new python. |
| 13 |
> |
| 14 |
>> This could certainly be done by patching the existing eclass, but |
| 15 |
>> mgorny wants to use new eclass names instead of keeping the |
| 16 |
>> current one. Hence the rename. I think that's about it.. |
| 17 |
> |
| 18 |
> |
| 19 |
> In that case we are missing 95% of the features of python.eclass. |
| 20 |
> |
| 21 |
|
| 22 |
Aha, but do we really -need- 95% of the features? :) Personally |
| 23 |
(this is my investment in this project) I'd just like to see |
| 24 |
non-distutils ebuilds needing python support using PYTHON_TARGETS. |
| 25 |
Also, I'd like to see that anything at all which new-distutils |
| 26 |
(whatever it be called) might need the old python.eclass for be |
| 27 |
integrated into new-distutils (probably via new-python). |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 30 |
|
| 31 |
iF4EAREIAAYFAlBnGKkACgkQ2ugaI38ACPCUGQD/f2tf7bjyxkq52In7OrH+nDSL |
| 32 |
nWLUWc9btwRm3Uuyd3AA/3tFI8uOiqpAVS7Ze4ScCt1UHi7LdvXgYGZRxPbJUbvS |
| 33 |
=4o7s |
| 34 |
-----END PGP SIGNATURE----- |
Archives