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

[Hisham Muhammad]

On 7/24/07, Samuel A. Falvo II <sam.falvo at gmail.com> wrote:
> On 7/24/07, MJ Ray <mjr at phonecoop.coop> wrote:
> > My current opinion is that any project on more than one continent is
> > large enough to benefit from a distributed version control system.
>
> Personally, I could go either way with this particular project.  The
> question boils down to this: how often do we branch?
>
> In software development, branches occur all over the place, all the
> time.  But in package management?  That's a different consideration.
>
> If branching to a wide fanout is not required, then SVN may provide
> just as fruitful a service as git would.  This is because, in this
> case, SVN is being used as a configuration management tool.  Remember,
> distributed systems were designed to solve the branching problem,
> first and foremost.

Oh, that's back on topic. :) No, I don't think we branch often in
package management. A branch in package management is a different set
of versions for recipes. We might want to maintain recipes for Glibc
2.X which was released with Gobo version A and recipes for Glibc
2.(X+1) which was used on Gobo (A+1). Since versions and revisions are
already stored separately in the recipes tree, there's no need to
branch the tree to handle this. Having two people working on different
branches of a recipe for the same version of the same package is
unlikely.

-- Hisham