Jack,
Excellent!!! You gave me the missing key. I didn't realize that the
program that commitinfo called was being executed in the workspace
directories where the files were being committed. Although it will take a
little work, I can create a network drive that everyone "mounts" that has
Perl and the appropriate Perl scripts.
This really helped. Thanks again.
-Scott
-----Original Message-----
From: Jack Christensen [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 31, 2000 4:40 PM
To: [EMAIL PROTECTED]
Subject: Re: Locking branches and/or trunk
The default directory a commitinfo script will start in is actually each
directory in your workspace in which there is a file to be committed.
If there are five files in five directories, it will fire up five
times. If there are five files in one directory, it will fire up once.
I missed the fact that you're working in a mixed OS environment. I know
that there are versions of PERL which function on both UNIX and
Windows. I would look at that. The trick might be to get PERL on
everybody's search path. I've succeeded doing something like this
getting triggers to work in a mixed UNIX/Windows environment when I was
working with ClearCase. I haven't tried it with CVS yet.
thanx,
jack c.
Scott Pyatt wrote:
>
> Jack,
>
> Correct me if I'm wrong, but that would assume the script somehow knew the
> location of the workspace in which the commit is taking place. Since
> anything that commitinfo kicks off is only passed the directory and file
> name, I don't know how you could derive the workspace directory. Of
course
> my situation is complicated by the fact that the repository is on a Sun
box,
> while the developers performing the commits are on NT system. Any
thoughts?
>
> Thanks,
> -Scott
>
> -----Original Message-----
> From: Jack Christensen [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 31, 2000 12:54 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Locking branches and/or trunk
>
> I simply wrote a script which is run by 'commitinfo'. It examined the
> CVS/Entries file to determine if all checked in files are on the correct
> branch.
>
> thanx,
> jack c.
>
> Scott Pyatt wrote:
> >
> > 1. Is there a way to lock a branch without affecting the other branches
or
> > the trunk?
> >
> > 2. Is there a way to lock the trunk without affecting the other
branches?
> >
> > There does not appear to be an intuitive method for accomplishing this
in
> > CVS. It appears I can limit commits on a directory by directory basis
> using
> > commitinfo. However, there is no version or branch information passed
to
> > the associated programs that commitinfo launches.
> >
> > My environment consists of the CVS repository on a SPARC Solaris 7.0
> system,
> > with the developers using WinCVS on NT systems. Thanks in advance.
> >
> > -Scott Pyatt
