Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Tue, 03 Jan 2006 12:22:35 +0100, Bo Berglund <bo.berglund at telia.com> wrote: >On Tue, 03 Jan 2006 09:24:16 +0100, Bo Berglund ><bo.berglund at telia.com> wrote: > >> >>2. The wording in the postcommit description is: >>"This will cause checkins to repository directories starting with >>cyclic-pages to update the checked out tree in /u/www/local-docs" >>My question here is the following: >>If one puts a line like this >> >>^SomeModule HEAD c:/test/shadow >> >>into the shadow script, will a commit to the module SomeModule >>*create* a shadow at the expected position or must one first check out >>a sandbox there and then the shadow action will just "update" it as it >>exists? >>If the latter is the case, will it then handle the addition of new >>directories or will the shadow just consist of the initially checked >>out tree with new updated versions of files? >> > >I now made a test that worked out very poorly: > >1) Added this line to the CVSROOT/shadow file: >^ModuleXX HEAD C:/DATA/USERS/CVSNT >and committed the file. > >2) Edited a file in my ModuleXX module and committed it. > >Nothing happened in C:/DATA/USERS/CVSNT it is still totally empty. >Is this how it is supposed to work? > Another couple of tests: 1) Checked out ModuleXX to C:/DATA/USERS/CVSNT 2) Edited a file in a different sandbox for ModuleXX and committed 3) Still no sign of the shadow update 4) Modified the shadow file to read: ^ModuleXX HEAD C:/DATA/USERS/CVSNT/ModuleXX 5) Like 2) 6) Like 3... :-( Seems like the shadow file does not operate at all.... /Bo (Bo Berglund, developer in Sweden)