[6839] in SIPB bug reports
Re: CVS for sipb.src
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon May 18 11:48:57 1998
To: chad brown <yandros@MIT.EDU>
Cc: bug-sipb@MIT.EDU
In-Reply-To: Your message of "Mon, 18 May 1998 06:27:15 EDT."
<199805181027.GAA00735@mary-kay-commandos.MIT.EDU>
Date: Mon, 18 May 1998 11:44:50 EDT
From: Greg Hudson <ghudson@MIT.EDU>
> there was some discussion today about putting the sipb locker
> sources into a CVS repository.
I've been thinking about doing this for the gnu locker.
Some obvious benefits are:
* You get semi-automatic merging of local changes into new
versions.
* Because of that, you can make slightly more extensive local
changes, e.g. coercing the build system into some standard
form a la Makefile.athena, without much added effort.
* You can set up automatic notification of changes, which in
turn lets you add maintainers you don't necessarily trust
quite as much to do the right thing.
And the pains in the butt are:
* Sometimes packages ship with .cvsignore files which cause
files in the distribution to be ignored during an import.
krb5 had this problem and BIND 8 still does. It's a bug, of
course, and it's fairly rare, but it's a problem you don't
get with more ad hoc arrangements.
* Sometimes packages have symlinks in them. CVS can't deal
with those.
* Not all that many people know the ins and outs of CVS,
especially with regards to the subtleties of imports.
Expect to need a CVS guru on hand when anyone imports a new
version of a software package, at least at the beginning.
