Adam Bregenzer wrote:
> Not at all. The server that holds the cvs repository also has apache
> runing on it. When a commit occurs each file that is committed is
> copied into a seperate directory. That directory is the DocumentRoot
> for apache. That way, when a change is committed it is automagicall
> viewable by browsing to the cvs server. The point is that one who does
> not edit the site manages and approves the site. Currently that
> individual runs cvs rtag when the site is in a producation ready state.
> Then a script is run that does a cvs export with that tag and posts it
> to the live site. It has nothing to do with the client, it's all
> *server* side. I see no reason for it to bve tied to an update, I don't
> even know how to execute a server-side script on update and wouldn't
> want to anyways.
At this point I begin to understand what you are talking about. What
you are doing is overloading CVS to be an archiving system *and*
distribution system. This is, to be blunt, bad engineering. What you
should do is write a script which commits the file and, upon
successful commit, updates DocumentRoot (or it could be a smart script
that only updates the relevant directory). So you already *do* have a
working copy, you've just built it the wrong way.
/|/|ike
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
