Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 May 2008 19:12:58 -0400
From:      ari edelkind <edelkind-freebsd-hackers@episec.com>
To:        freebsd-hackers@freebsd.org
Subject:   Re: using git for freebsd development
Message-ID:  <20080514231258.GB79355@episec.com>
In-Reply-To: <482B5E08.9000309@icyb.net.ua>
References:  <482B5E08.9000309@icyb.net.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
avg@icyb.net.ua wrote:

> The following can be considered as a followup to the excellent 
> FreeBSD/GIT wiki page:
> http://wiki.freebsd.org/GitConversion
> 
[...]
> All of the tools either required source CVS repository to be available 
> locally or worked much faster in that case, so the first thing to do was 
> to get src-all from my local cvsup mirror. Easy.

Everyone who tries converting freebsd's cvs repository to joe-random-RCS
attempts to import the entire source tree as a single project.
Honestly, it covers too broad a spectrum.  Separate these projects into
the cvsup collections: src-sys, src-bin, src-lib, etc..  You won't be
able to simply tag a single branch into a full system release without a
wrapper script to handle your collections, but that's a small price to
pay for the added robustness, separation of privilege, and smaller-scale
potential for conflict.

In fact, even src-bin may be too broad, and it may make sense to have
separate projects within the collection hierarchy.  This would, at
least, make reparenting projects (say, from src-bin to src-usrbin)
easier.

ari




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080514231258.GB79355>