-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 29/09/12 11:45 AM, hasufell wrote:
> On 09/29/2012 05:37 PM, Ian Stakenvicius wrote:
> 
>> There isn't so much a problem with the current
>> python-distutils-ng eclass but rather it's to expand it to a more
>> comprehensive replacement for both distutils and python eclasses.
>> In order to do that efficiently, most of the core functionality
>> should be moved so that the new distutils is more like a wrapper
>> to the new python.
> 
>> This could certainly be done by patching the existing eclass, but
>>  mgorny wants to use new eclass names instead of keeping the 
>> current one.  Hence the rename.  I think that's about it..
> 
> 
> In that case we are missing 95% of the features of python.eclass.
> 

Aha, but do we really -need- 95% of the features?  :)   Personally
(this is my investment in this project) I'd just like to see
non-distutils ebuilds needing python support using PYTHON_TARGETS.
Also, I'd like to see that anything at all which new-distutils
(whatever it be called) might need the old python.eclass for be
integrated into new-distutils (probably via new-python).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlBnGKkACgkQ2ugaI38ACPCUGQD/f2tf7bjyxkq52In7OrH+nDSL
nWLUWc9btwRm3Uuyd3AA/3tFI8uOiqpAVS7Ze4ScCt1UHi7LdvXgYGZRxPbJUbvS
=4o7s
-----END PGP SIGNATURE-----

Reply via email to