|
Boost : |
From: Brad King (brad.king_at_[hidden])
Date: 2002-05-10 15:33:12
> The only problem left is where to put the script. It can be checked
> in, but there has to be a server-side checkout of it somewhere.
As an addition to my previous message, I remembered how to get the
pre-commit script to show up on the server side. In the CVSROOT checkout,
there is a file called "checkoutlist" that tells the server what files in
CVSROOT should be checked out on the server side.
Here is how to add the pre-commit check:
1.) Checkout the CVSROOT admin directory on a client.
cd $BOOST_ROOT
cvs co CVSROOT
cd CVSROOT
2.) Write your commit checker script, make it executable, and add it.
chmod 755 boost_commit_checker.sh
cvs add boost_commit_checker.sh
3.) Edit the checkoutlist file and add this line:
boost_commit_checker.sh Server could not checkout pre-commit checker.
4.) Edit the commitinfo file and add this line:
ALL $CVSROOT/CVSROOT/boost_commit_checker.sh
5.) Commit all these changes. The server will update its administration
database automatically.
cvs commit -m "Added pre-commit checker."
I suggest that you get this setup with an empty script like
#!/bin/sh
exit 0
to make sure you don't lock yourself out. You can then write and test the
script separately. The pre-commit check program must be able to execute
on the SERVER, so you need to know that your script will run there.
-Brad
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk