[gobolinux-users] Call for volunteers: would you like to be a recipe committer?

[Carlo Calica]

<Big thread.  I mostly skimmed. >

On 7/21/07, Samuel A. Falvo II <sam.falvo at gmail.com> wrote:
> On 7/21/07, hisham.hm at gmail.com <hisham.hm at gmail.com> wrote:
>
> > Savannah CVS to the gobolinux.org SVN sometime in the future). So I
> > guess we're heading into offtopic territory a little.
>
> Indeed, but it's interesting nonetheless.  :)
>

I agree this thread is interesting but fairly offtopic.  We had a
similar discussion many moons ago. One of the main goals of recipe
maintenance is to provide a "central sync" for all contributors.  Ease
of distributed branches was NOT a deciding factor.  Linus's, to
paraphrase, "SVN devs are stupid" comment really misses the point.  It
may be stupid for the kernel but there are many cases where it isn't.
In the original thread, I was pro distributed.  Now I'm not.  We're
not large enough to benefit from distributed SCM.  In fact splitting
the recipe store to a handful of repos across the internet is a
downside.  It'll create more work to sync to the final repo.

For a very long time, Lucas has been fine tuning the recipe workflow
and tools for SVN.  I don't want to throw that away.  Let's use that
now and reevaluate next year or later.  We need more action and less
planning (something I'm the most guilty of).

WRT, using local branches to maintain local patches.  Its interesting
but I don't think it a long term solution.  It requires detailed
knowledge of the SCM and Compile/Recipes.  Definitely guru territory.
Hopefully we can do something easier.

WRT, using quilt.  I see something like that being integrated in
Compile directly.  Our use of ordered patches is already similar.


-- 
Carlo J. Calica