| 1 |
[ Leaving message intact as I feel it should be re-iterated even yet |
| 2 |
again :p ] |
| 3 |
On Nov 1, 2005, at 8:33 PM, Brian Harring wrote: |
| 4 |
|
| 5 |
> On Tue, Nov 01, 2005 at 02:10:03PM -0600, Kito wrote: |
| 6 |
>> I'll let Brian answer this, but I'm fairly certain there is no chance |
| 7 |
>> of this making it into the 2.0 series, 2.1 is dead, so 3.0 will have |
| 8 |
>> to be our saviour (boooo! hsssss! bad pun) |
| 9 |
> |
| 10 |
> No way in hell on 2.0; 2.1 was released dead (the major changes of it |
| 11 |
> are a year old), 3.0 would be the only _potential_ portage target. |
| 12 |
> |
| 13 |
> Why did I say potential? |
| 14 |
> |
| 15 |
> Cause I'm after making an ancillary point so everyone is on the same |
| 16 |
> page here- portage will *not* have any prefix support without the |
| 17 |
> ebuild changes being vetted by gentoo community. |
| 18 |
> |
| 19 |
> What's being worked on is a prototype- the prototype will be useful on |
| 20 |
> it's own, but the main point of it is demonstrating that it's doable |
| 21 |
> and the pros/cons of it. |
| 22 |
> |
| 23 |
> Please keep this in mind. Bit of a reality check (kito and I are |
| 24 |
> operating under this)- comments of the sort "when portage supports |
| 25 |
> prefix "... |
| 26 |
> |
| 27 |
> Portage will only mainline support PREFIX if devs agree to the |
| 28 |
> underlying |
| 29 |
> ebuild changes. So... help make it clean, but be aware of the |
| 30 |
> rules being |
| 31 |
> operated under please. |
| 32 |
> ~harring |
| 33 |
|
| 34 |
This is the other area where the more help we have the better. If |
| 35 |
anyone is having doubts about jumping in on the tech side of prefix |
| 36 |
support, you can also put your lawyer hat on and start researching |
| 37 |
and preparing our case to the jury. We will need an absitively |
| 38 |
posolutely 100% bullet proof GLEP that covers every aspect of the |
| 39 |
impact this will have on the Gentoo project and community as a whole. |
| 40 |
|
| 41 |
Sooooo, maybe we should actually start a sort of community drafted |
| 42 |
GLEP, slowly and methodically nailing down all the benefits, and all |
| 43 |
the drawbacks, of this being adopted. No need to rush it, it can just |
| 44 |
be something that gets improved as we go along, so when it comes time |
| 45 |
to show our work and go through the official GLEP process, we aren't |
| 46 |
caught with our pants down. |
| 47 |
|
| 48 |
A good start would probably be going back through previous ML archive |
| 49 |
threads and making sure all the relevant discussion is incorporated. |
| 50 |
|
| 51 |
Hmmm...a GLEP wiki page for this could be interesting....might be |
| 52 |
easier than trading diffs back and forth via ML. |
| 53 |
|
| 54 |
--Kito |
| 55 |
-- |
| 56 |
gentoo-osx@g.o mailing list |
Archives