| 1 |
On Tue, Jun 19, 2012 at 08:54:07PM +0200, Thomas Sachau wrote: |
| 2 |
> Ciaran McCreesh schrieb: |
| 3 |
> > On Tue, 19 Jun 2012 20:16:39 +0200 |
| 4 |
> > Thomas Sachau <tommy@g.o> wrote: |
| 5 |
> >> Since there is again no response at all, it seems like everyone is ok |
| 6 |
> >> with this, so i will propose to add this to the next council agenda |
| 7 |
> >> for EAPI-5 addition. |
| 8 |
> > |
| 9 |
> > Got a diff for PMS? |
| 10 |
> > |
| 11 |
> |
| 12 |
> Last time you only requested enough details for implementation, you did |
| 13 |
> not require a PMS diff, so i wrote more details for the implementation. |
| 14 |
> |
| 15 |
> If you, Brian (for pkgcore) and zmedico accept this for EAPI-5, i might |
| 16 |
> look into creating a diff against PMS but until then, i dont want to |
| 17 |
> waste my time, especially since noone commented on the implementation |
| 18 |
> details or the technical details and any change would require even more |
| 19 |
> work to rework/adjust the PMS diff. |
| 20 |
|
| 21 |
You need a glep here frankly; per the norm, if you want things to move |
| 22 |
faster, then put in time- aka, generate a patch against PMS, write a |
| 23 |
patch for portage, etc, you get the idea. The bit re: a PMS patch is |
| 24 |
mostly that in looking at your proposal... well, I personally don't |
| 25 |
want to write that patch (nor do I suspect ulm/ciaran do either). |
| 26 |
|
| 27 |
One thing to note; this has been posted for all of 2-3 days; that's |
| 28 |
not exactly much time for 1) people to comment, 2) people to frankly |
| 29 |
comprehend the quite dense description you wrote. |
| 30 |
|
| 31 |
Please write a glep covering details of the implementation, |
| 32 |
background, preferablly why this route over others. Bluntly... clue |
| 33 |
everyone else in rather than hoping they'll just sign off on a fairly |
| 34 |
opaque list of things. :) It'll be useful for dev education also- |
| 35 |
which is a bit of a requirement for stuff of this sort considering |
| 36 |
it's not going to be a magic deploy/shit works everywhere situation I |
| 37 |
suspect. |
| 38 |
|
| 39 |
Would also be useful getting commentary from crossdev folk considering |
| 40 |
your solution is intended to be (best I can tell) full cross |
| 41 |
compilation support, and they've been leading that front for many, |
| 42 |
many years. |
| 43 |
|
| 44 |
Cheers- |
| 45 |
~brian |
Archives