[cvsnt] Re: Modules and Shared Libraries - tagging strategy?

Torsten Martinsen torsten at tiscali.dk
Thu Nov 11 21:27:37 GMT 2004


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.


Bo Berglund wrote:

>So what we have tried to do is this:
>In the main project folder we create a batch file we call
>dependentfiles.bat. This contains a bunch of cvs checkout commands
>that when run will create a number of folders *below* the main project
>folder containing the shared code (these are sources, not compiled
>binaries).
>
>When someone checks out the main project he will also get the batch
>file and the first thing he has to do is execute that. When that is
>done he has all the files needed for the project inside the main
>project folder.
>Note that the batch file is done such that it checks out only those
>files that are actually needed from the shared modules.
>
We also used this approach previously, but have found that using "cvs 
import" is a superior solution - after all, cvs import was designed for 
tracking third-party sources.

-Torsten



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