[cvsnt] Export doesnt work properly anymore (2.0.4)

Bo Berglund Bo.Berglund at system3r.se
Wed Jun 25 19:38:52 BST 2003

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.

The script files I use are simple Windows batch files. Any given
software product setup compilation starts with executing the bootstrap
batch file, which exports the main batch file and executes it.
The main batch file needs to export all the needed files and it must
be maintained in sync with the ISS file for InnoSetup.
Both the batch files use cvs export for their work.

I can think of a number of tricks to fix this problem, but the simplest
is actually not to upgrade beyond 1.11.3b72 on our workstations until
the -N fix is in CVSNT. Then all of us will upgrade to 2.0.5 (or whatever
the version will become) and all will work without changing the scripts.
In my case what I had to do was shut down my local CVSNT server on my laptop
and then rename the CVSNT folder, create a new CVSNT folder and drop the
files from 1.11.1b72 into this. It is alreaduý on Path so I'm done for
the moment.
Most developers use WinCvs but that installation does not put anything on the
path so they can get an update for just the command to work properly and it won't
affect WinCvs either.


-----Original Message-----
From: Mitch Davis [mailto:Mitch.Davis at EXTEL.COM.AU]
Sent: den 25 juni 2003 15:40
To: Bo Berglund; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: RE: [cvsnt] Export doesnt work properly anymore (2.0.4)

> From: Bo Berglund [mailto:Bo.Berglund at system3r.se] 
> I think we have upwards of 20-40 different script files that 
> make use of the -N flag. 
> Editing these will not be a simple task... 
> The idea is that all you need on a workstation to make a 
> setup is cvs and the bootstrap scriptfile. (which can be 
> checked out in a regular sandbox so it can be 
> updated if need be). 
As a temporary workaround, can your script check the 
version of CVS, and use "sed" to patch itself 
according to which version of cvs export will work 
It's quite easy to convert "cvs export -r HEAD 
-d WSMDB -N Redist/MSDE2000" to "cvs export -r HEAD 
-d WSMDB/Redist Redist/MSDE2000" using sed.  If I 
knew more about how the two lines relate to each 
other, I can tell you the sed expression. 
The information contained in this message and any attachments is 
confidential and intended for the named recipient(s). If you have received 
this message in error, please contact sender by return e-mail and 
destroy the message and any attachments. 
Any opinions or undertakings expressed in this message are those of the 
individual sender except where the sender expressly and with authority 
states them to be the opinions of Extel. 

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook