Chris Cameron wrote:
> > My original purpose was to perform an automatic checkout (in a test bed)
> > every time someone was doing a commit. Doing this with "commitinfo" did
> > not seem possible since "cvs commit" recursively commit all modified
> > files, if 100 files are commited at once, I don't want commitinfo to
> > launch 100 checkouts (maybe should I simply run one "update" per
> > "committed" file?). So I decided to go for a crontab (not as good, user
> > may have to wait 10mn to see their changes published in the test bed).
>
> Well, the other way to do things, as described in cederqvist, is to use
> loginfo, not commitinfo.
How did I miss this one, the cederqvist is my current reading!
> loginfo only runs after the commit succeeds and cederqvist gives an example
> of how to use it for an automated checkout. In our loginfo file we have
> the following line to do this (excuse any mailer wrapping, this should be
> on one line):
>
> WWW/* ($CVSROOT/CVSROOT/cvslog.sh ${USER} ALL %{};(cd /WWW ; sleep 5; echo
> `pwd` Updated by ${USER}-`date` ; /usr/local/bin/cvs -nq update -d ;echo
> --------------------- ; /usr/local/bin/cvs -q update -d ;echo
> =================================)>>$CVSROOT/CVSROOT/LOGS/WWW_update.log
> 2>&1 &)
This works perfect and actually I have discovered that my login/password
issue can easily be solved by not using the "pserver" protocol since
automatic-checkout can only be performed on the computer the CVS
repository is (or on a file system mounted on this computer). So now I
do a:
cvs -d /home/cvs/blabla upadate -d ....
commitinfo is very powerfull, not using it is like having a web server
without CGI :)
Thank you all for your help.
Mikael
--
Mikael Grave Tel. (613) 731-4046 http://www.webmotion.com
Webmotion Inc. Fax. (613) 260-9545 [EMAIL PROTECTED]
`----------------------------------------------------------------'
