Re: Latest Versions in Separate Folder than Repository

[Pierre Asselin]

address@hidden wrote:

> I've had a CVS set up, but an idea crossed my mind.  Is there a way to
> make it so that cvs will keep the latest versions of the files in the
> repository (in their working form, not diff form) on the server in a
> folder separate from the repository?

With the loginfo file.  The on-line manual has a worked example
that updates a reference sandbox on every commit.

    https://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_18.html#SEC158

The reference sandbox can even be on another machine, if the server
has the ability to run remote commands on it.

> For instance, with a repository folder 'C:\CVSRepo' with module 'code',
> whenever someone commits a change to the module would it be possible to
> have the module 'code' be checked out on the cvs server in a folder
> separate from 'CVSRepo'?  Ie 'C:\latestCode'.

On Windows ?  Oops.  Well, the loginfo file should work as everywhere
else, but you'll have to translate the bash example in the docs to
some other scripting hack supported on Windows.  I wonder if the
wincvs folks have a similar example in their docs?  I found the
exact same example on their site, but not translation to Windoish.

Basically, your loginfo hook has to *schedule* an update of the
reference sandbox after a small delay and exit before the update
begins.  That allows the triggering commit to release its repository
lock before the update fires up.

-- 
pa at panix dot com