[oclug] complicated CVS setup

[Brenda J. Butler]

On Thu, Apr 26, 2001 at 09:23:22AM -0400, Bart Trojanowski wrote:
> On Wed, 25 Apr 2001, David F. Skoll wrote:
> 
> > On Wed, 25 Apr 2001, Bart Trojanowski wrote:
> >
> > > Ideally I want the user to be forced to update, recompile, test, then
> > > commit.  However I know I cannot force them to do the compile/test steps
...
> > CVS will not let you commit without updating, so I don't see the purpose
> > of this.
> 
> I want to force people to test before they commit.  And what is the point
> of testing if you don't have the latest files in the project.

David was trying to say that cvs's default behaviour already
does what you want.  See the following paragraph from the man page:

	  commit  verifies  that the selected files are up to
              date with  the  current  revisions  in  the  source
              repository;  it  will  notify you, and exit without
              committing, if any of the specified files  must  be
              made  current first with `cvs update'.  commit does
              not call the update command  for  you,  but  rather
              leaves that for you to do when the time is right.

And I know from using cvs that this is indeed the case.

As for "email notifications on watched files" search for
"commitinfo" and "cvswrappers" in the man/info page for cvs.
I haven't used them myself but the facilities are there.

-- 
bjb at achilles.net
Consider registering as a bone marrow donor
http://www.bloodservices.ca/english/ubmdr