Gentoo Archives: gentoo-scm

From: Donnie Berkholz <dberkholz@g.o>
To: Mike Auty <ikelos@g.o>
Cc: gentoo-scm@l.g.o
Subject: Re: [gentoo-scm] Status of the project?
Date: Fri, 23 Jan 2009 18:46:10
Message-Id: 20090123184606.GA13522@comet
In Reply to: [gentoo-scm] Status of the project? by Mike Auty
On 11:22 Fri 23 Jan     , Mike Auty wrote:
> So what's the current state of things? Apparently[1] portage is now > capable of having not only a git repo to commit to, but actually using > git as the primary repo for users (rather than using rsync). Great work > Zac, thanks! > > Do we have a plan for keeping this moving? What things are we lacking > at the moment that mean we're not ready to establish a testing > environment? If we've got repoman support, and we've got portage > support, presumably it's just the bits in the middle (server-side > metadata generation, QA tests?) that need doing?
And the plan ...
> I'm glad that we're making progress (Daniel seems to be pushing this, > which is good),
Daniel isn't pushing much on our end, unless if by pushing you mean doing things that won't be suitable for us because last I heard, he's dropping all history from the Funtoo tree. His git patch for portage was helpful, though a very small part of the work to be done.
> but I'd like to know what tasks we internally have left to consider, > and put together a list of all the things we need to do to proceed. > Once we've got that people will be able to pick things they can help > with and we might get the ball moving a bit faster. Thanks...
OK. 1. Decide whether the existing tree layout is suitable for and best in a git world. If not, what is? I have done some thinking about this at <>. 2. Decide whether the existing development model is suitable for and best in a git world. If not, what is? I have done some thinking about this at <>. 3. Switch to the best layout and development model. Issue 3 is the easy one. -- Thanks, Donnie Donnie Berkholz Developer, Gentoo Linux Blog:


Subject Author
Re: [gentoo-scm] Status of the project? Mike Auty <ikelos@g.o>