[darcs-users] Centralized Darcs usage

Sébastien Pierre sebastien at xprima.com
Fri Apr 21 13:55:17 UTC 2006


Le jeudi 20 avril 2006 à 23:55 +0100, Jamie Webb a écrit :
> On Thu, Apr 20, 2006 at 06:40:44PM -0400, Sébastien Pierre wrote:
> > Le jeudi 20 avril 2006 à 14:57 -0700, Jason Dagit a écrit : 
> > 
> > > You could nest the repositories but I would recommend against it.  I
> > > think in your case everyone on the team will end up checking out a
> > > full copy of everything, modifying his or her part and then checking
> > > that piece in again.  Other than that, you could manually fator things
> > > out in to seperate libraries and such.
> > 
> > The problem here is that there are many, many small projects that should
> > be versionned under a single repository.
> 
> Are you sure about this part? It's normal to have a separate darcs
> repo for each project. What do you expect to gain by lumping
> everything in together?

At first, there are hundreds of projects, which are mainly small
scripts, which sometime have inter-dependencies. In this case, it seems
to me as overkill to have one repository per project, and I am even not
sure to be able to reference a "meta-version" that says projects-v1.5 is
composed of (p1-v0.3, p2-v1.7, p3-v1.0, ...., pN-v2.0).

These projects may be grouped into a small number of repositories, but
then I would still need the ability to compose repositories, so that I
could do projects = p1 + p2 + p3 + ... pN.

 -- Sébastien 





More information about the darcs-users mailing list