[EMAIL PROTECTED] (Larry Jones) writes:
> 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 out
> copy" in the manual won't work?
>
> http://www.cvshome.org/docs/manual/cvs_18.html#SEC171
My problem with that was that it was (potentially) run as a different
user each time, resulting in permission errors (since the users don't
have g+w in their umask). I just wrote a short setuid program that
executed the same command.
I also seem to recall that it gets called once for each file, which
leads to bunches of "waiting for xxx's lock on yyy" messages when a
single cvs commit ends up committing multiple files (since multiple
copies of it are running at once).
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
