> Nick Flowers writes:
> >
> > I'm modifying the server so that a developer committing
> > a change automatically causes an export to our staging
> > webserver.
>
> Why? Is there some reason the method shown in "Keeping a
> checked outcopy"
> in the manual won't work?
> http://www.cvshome.org/docs/manual/cvs_18.html#SEC171
>
Yes. It does not work. I used this originally. It only
updates existing documents. As soon as a new documnet is created
it does not get a copy in the staging area.
I have the following in loginfo
^wwwroot ( date; cat ; ($CVSROOT/bin/tedcheckin wwwroot %{s V v})&)
>> $CVSROOT/CVSROOT/updatelog 2>&1
And the script does:
echo "About to do cvs cmd "`date`
rm -rf ${dir}
mkdir ${dir}
chmod 770 ${dir}
cvs checkout ${dir}
echo "Done cvs cmd `date`"
Messy but we had a case where somebody edited (finger slipped honest)
the 'staged' copy in such a way that it was Read-Only this stopped
all changed getting staged and produced some hard to track bugs.
***********************************************************************************
The contents of, and the information contained in this email and any files transmitted
with it are confidential and legally privileged, and are sent for the personal
attention
of the addressee(s). If you are not the intended addressee, any use, disclosure or
copying of this document is unauthorised.
Thank you
NTL
***********************************************************************************
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
