1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 29/09/12 09:49 AM, hasufell wrote: |
5 |
> On 09/29/2012 12:49 PM, Michał Górny wrote: |
6 |
>> On Sat, 29 Sep 2012 11:20:31 +0100 Markos Chandras |
7 |
>> <hwoarang@g.o> wrote: |
8 |
> |
9 |
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 |
10 |
>>> |
11 |
>>> On 09/29/2012 09:53 AM, Micha? Górny wrote: |
12 |
>>>> Hello, |
13 |
>>>> |
14 |
>>>> Instead of the floating patches and p-d-ng modifications I |
15 |
>>>> sent earlier, here are the two complete (so far, well, |
16 |
>>>> initial :P) eclasses for review. |
17 |
>>>> |
18 |
>>>> They are designed as 'mostly' drop-in python-distutils-ng |
19 |
>>>> replacement. |
20 |
>>>> |
21 |
>>> Hi, |
22 |
>>> |
23 |
>>> Are you saying that you are going to remove the |
24 |
>>> python-distutils-ng eclass in favour of the new eclasses? I |
25 |
>>> don't quite understand the reasons to be honest. |
26 |
> |
27 |
>> The reason is simple -- I can't fix it without changing the API. |
28 |
>> Changing the API on a live eclass is confusing, and considering |
29 |
>> that it is not used by many packages, it's easier to lastrite |
30 |
>> it. |
31 |
> |
32 |
>> Also, this fixes the name not to have any '-ng' nor '-ds9'. |
33 |
> |
34 |
> |
35 |
> What are the reasons to change the API in the first place? There |
36 |
> has to be a good reason, cause this will involve yet another |
37 |
> migration of many ebuilds. I don't see any bugreports. |
38 |
> |
39 |
> I fear this will cause more confusion, i.e. some ebuilds using the |
40 |
> old distutils, some using python-distutils-ng and some using |
41 |
> distutils-r1 resulting in weird tree behavior. |
42 |
> |
43 |
|
44 |
Given that at present, distutils-r1 and python-distutils-ng have |
45 |
identical end-results, I think that the introduction of distutils-r1 |
46 |
to the tree should also involve a sed against all the existing ebuilds |
47 |
using python-distutils-ng to move them to the new eclass. Then |
48 |
python-distutils-ng only needs to remain to support overlays. |
49 |
|
50 |
-----BEGIN PGP SIGNATURE----- |
51 |
Version: GnuPG v2.0.19 (GNU/Linux) |
52 |
|
53 |
iF4EAREIAAYFAlBnA1YACgkQ2ugaI38ACPBtCgD/UXW804+tsTOnI0RtfWfhiewK |
54 |
a0W9DXplPRprWYZg4mQBAIWbRf+AJDrIqGvELiwt3p0FXChbCYypHDmm3tb8ljxL |
55 |
=isBB |
56 |
-----END PGP SIGNATURE----- |