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