RE: CVS commitinfo trigger question

[Shubhabrata Sengupta]

I get the branch information out by parsing the CVS/Entries file on the server side. Though it exposes me to the innards of the Entries file, I don’t think the format will change from one release of CVS to the other. So, I am okay with the risk that entails.

 

Shubho

 

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Bill Buie
Sent: Thursday, November 29, 2001 11:11 PM
To: address@hidden
Subject: CVS commitinfo trigger question

 

So far I have not found anyone who can answer the question below.  If you can answer the question, I would greatly appreciate it, or if you can't then I would also appreciate a pointer to someone who could.

 

I want to use a commitinfo trigger that will require a script of my design to complete with zero status before permitting checkins to certain branches.  The most obvious way to tell what branch a file is being committed to would be with the cvs status subcommand, but I have run into a catch.  The cvs commit subcommand locks the repository such that the commitinfo script hangs when it tried to invoke the cvs status subcommand.

 

I have found a way to do this which I don't like: modify the source on the client and the server such that the sticky tag and version is passed on the command line to the script invoked by commitinfo.  However, I would much prefer to use unmodified CVS with its standard protocol for communications between client & server and permit my users some flexibility with regards to their favorite CVS client.  Note that I explicitly want the script to run on the server, which will be running Linux, and not the client, which may be running Linux or Windows.
 
Surely I am not the only CVS user to attempt this. What is the standard way of doing it?

Thanks very much,

 

    --Bill