[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tag locking change

From: Mike Ayers
Subject: Re: Tag locking change
Date: Wed, 09 Oct 2002 14:55:22 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]