1 |
On 12/26/2009 05:15 AM, Thomas Sachau wrote: |
2 |
> On 12/26/2009 11:25 AM, Fabian Groffen wrote: |
3 |
>> On 25-12-2009 15:00:36 +0100, Thomas Sachau wrote: |
4 |
>>> Did you actually read my lines? I did NOT request an ACK to add it to |
5 |
>>> PMS and next EAPI with a complete spec. zmedico also has no problem |
6 |
>>> with having a look and adding it, but since he was once forced to |
7 |
>>> remove an added feature, he now wants a council-ok before adding and |
8 |
>>> improving it in testing branch of main tree portage. |
9 |
>> |
10 |
>> >From my experience they just want to get some grip on the issue. A |
11 |
>> formal description helps sometimes. |
12 |
> |
13 |
> As i already said: My implementation is not final nor do i request some PMS changes or EAPI bump for |
14 |
> it. I simply want some more help and feedback by getting it in the 2.2_rc* branch of portage and |
15 |
> zmedico just wants an ok from council, so that they wont force him to remove it again. |
16 |
|
17 |
The council needs to approve the merging of multilib support into |
18 |
mainline portage since ebuild developers will be expected to |
19 |
help/cooperate in fixing any issues that may arise due to |
20 |
interaction with the new multilib behavior. The role of imposing new |
21 |
expectations like this belongs to the council, not to me or the |
22 |
portage team. |
23 |
-- |
24 |
Thanks, |
25 |
Zac |