[oclug] complicated CVS setup
Gilles J. Seguin
segg at infonet.ca
Thu Apr 26 14:10:12 EDT 2001
Bart Trojanowski wrote:
>
> On Wed, 25 Apr 2001, Dan York wrote:
> >
> > This will happen automagically. If the user does a commit to an out of date
> > file and there is NO conflict, then the changes the user made are committed
> > and merged with the changes in the repository. The user will wind up with
> > an updated file in their local working copy. (so in this case there was no
> > reason necessarily for them to do a 'cvs update' first)
>
> Perhaps I did not introduce my problem sufficiently... I want to setup a
> policy that prevents people from commiting before an update. I know that
> the changes will be preserved... but the functionality of the result may
> not be. Say I have a function that is longer than 3 lines. I can easily
> come up with case scenarios where the commit before an update with 2
> developers does not cause a colision but will screw things up in the
> binary once it is executed. This has happened frequently enough here
> at work with a dozen people.
User with write access can have a script that parse the result of
$ cvs -n commit mymodule
example of setup with script
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/lesstif/CVSROOT/
> I appriciate the info you provided below... That will come in helpful...
> yes I know I should have RTFM. :)
>
> > So the net is that for the first item, CVS should already do this for you.
> > If you *really* wanted to do something else, I think you would modify the
> > "commitinfo" file in the CVSROOT directory in your repository. See:
> >
$ gv /usr/share/doc/cvs-1.11/cvs.ps
cvsclient.ps cvs-paper.ps
$ man cvs
> > http://cvshome.org/docs/manual/cvs_18.html#SEC165
> >
> > > second, allow for getting email notifications on watched files.
> >
> > I would look at:
> >
> > http://cvshome.org/docs/manual/cvs_10.html#SEC89
> >
> > and specifically:
> >
> > http://cvshome.org/docs/manual/cvs_10.html#SEC91
> >
> > Ultimately I believe you'll need to modify the 'notify' file in your
> > CVSROOT dir in your repository. I would also suggest looking at:
> >
> > http://cvsbook.red-bean.com/cvsbook.html#Watches__CVS_As_Telephone_
> > http://cvsbook.red-bean.com/cvsbook.html#Commit_Emails
> >
> > Hope that helps,
> > Dan
More information about the OCLUG
mailing list