1 |
Brian Harring schrieb: |
2 |
> On Tue, Jun 19, 2012 at 08:54:07PM +0200, Thomas Sachau wrote: |
3 |
>> Ciaran McCreesh schrieb: |
4 |
>>> On Tue, 19 Jun 2012 20:16:39 +0200 |
5 |
>>> Thomas Sachau <tommy@g.o> wrote: |
6 |
>>>> Since there is again no response at all, it seems like everyone is ok |
7 |
>>>> with this, so i will propose to add this to the next council agenda |
8 |
>>>> for EAPI-5 addition. |
9 |
>>> |
10 |
>>> Got a diff for PMS? |
11 |
>>> |
12 |
>> |
13 |
>> Last time you only requested enough details for implementation, you did |
14 |
>> not require a PMS diff, so i wrote more details for the implementation. |
15 |
>> |
16 |
>> If you, Brian (for pkgcore) and zmedico accept this for EAPI-5, i might |
17 |
>> look into creating a diff against PMS but until then, i dont want to |
18 |
>> waste my time, especially since noone commented on the implementation |
19 |
>> details or the technical details and any change would require even more |
20 |
>> work to rework/adjust the PMS diff. |
21 |
> |
22 |
> You need a glep here frankly; per the norm, if you want things to move |
23 |
> faster, then put in time- aka, generate a patch against PMS, write a |
24 |
> patch for portage, etc, you get the idea. |
25 |
|
26 |
Since multilib-portage code is just a git branch for the portage code, i |
27 |
effectively have a patch for portage. ;-) |
28 |
|
29 |
|
30 |
Before i start investing more time, a question to the PM developers: |
31 |
|
32 |
Do you prefer having everything hardcoded in PMS or can you accept |
33 |
outsourcing bigger code pieces into some sort of eclass (i am thinking |
34 |
about some external code base, which can be duplicated by the package |
35 |
manager with internal code, but has to be used, if the external eclass |
36 |
has a newer version/revision then the duplicated internal code)? |
37 |
|
38 |
I am especially thinking about the setup of the environment and the code |
39 |
details for the wrappers for binaries and headers, hardcoding those |
40 |
details into PMS makes it hard to change/fix issues later on. |
41 |
|
42 |
-- |
43 |
|
44 |
Thomas Sachau |
45 |
Gentoo Linux Developer |