Re: CVSNPupd configuration help

On Mon, 20 Nov 2006 22:17:15 +0100, Bo Berglund <[email protected]>
wrote:

>>On Sun, 19 Nov 2006 23:44:28 -0800 (PST), mohammed ali
>><[email protected]> wrote:
>>
>>>Hi All,
>>>   
>>>  We are using cvsnt and wincvs for version controlling.I want 
>>> to get the latest version in a seperate folder as a shadow folder.
>>> I installed Cvsntupd but it is not working.
>>
>>If what you want is to have a location where the very latest files in
>>your module automatically are updated on each cvs commit then you
>>should use the "shadow" function in CVSNT.
>>It is designed for just this purpose and is part of the CVSNT server.
>>
>>HTH
>>
>>/Bo
>>(Bo Berglund, developer in Sweden)
>>
>
> Hi Berglund,
> I don't know how to configure it and about the shadow function in 
> cvsnt.Can u please help me
> 
> Thanks and regards
> Mohammed Ali

Do not send mail directly to me! Always send to the *list* only!
I will answer anyway (this time):

Here is a copy directly from the CVSNT documentation, which is
available from the Help/CVS Documentation menu item in WinCvs.
Did you ever read the CVSNT docs?


The shadow file
The CVSROOT/shadow file is used by the checkout plugin to specify
directories that will be automatically updated on checkout or tag.

In order for the shadow file to have any effect the "Automatic
checkout extension" plugin must be enabled in the CVSNT control panel.

Keeping a checked out copy
It is often useful to maintain a directory tree which contains files
which correspond to the latest version in the repository. For example,
other developers might want to refer to the latest sources without
having to check them out, or you might be maintaining a web site with
cvsnt and want every checkin to cause the files used by the web server
to be updated.

The way to do this is by having a line in the CVSROOT/shadow. Here is
an example (this should all be on one line):

^cyclic-pages HEAD /u/www/local-docs
This will cause checkins to repository directories starting with
cyclic-pages to update the checked out tree in /u/www/local-docs.

Note that if the shadow copy does not exist already it will be created
by the execution of the shadow command. Likewise if a shadow copy
exists and new directories have been added to the module then these
directories and files will also be checked out into the shadow copy.
So it will always be a true representation of the current state of the
module.

The shadow file works only on the physical file system level (inside
the repository). This means that a module specified in the regular
expression must match a physical module name in order to be
recognized.

For example if you have created virtual modules inside the
CVSROOT/modules file or CVSROOT/modules2 file you cannot specify such
a module name in the shadow file.


HTH

/Bo
(Bo Berglund, developer in Sweden)