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

Bo Berglund bo.berglund at telia.com
Thu Nov 11 19:35:26 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.


On Thu, 11 Nov 2004 11:12:13 -0500, "Williams, Tim"
<WilliamsTim at PRAIntl.com> wrote:

>Hi folks,
>
>I have a question about how best to use and manage a code library that
>is used in multiple projects.
> 
We have also the same or similar problem and we cannot use the modules
or modules2 file either, because:
- Our shared code is stored repositories that are separate from the
  main code repository.
- We also have several main repositories for different kinds of final
  product.

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.

When a developer works he can create branches on both the main module
files and on the shared files. He can aslo tag from the top and get
the same tag into all the files even across repositories (and even
across servers for that matter).

There is one problem we have not been able to solve and it is bugging
us a lot. It concerns the way Delphi components are used. We all have
components installed in Delphi beneath the Delphi7 program folder.
These are checked out from a repository where we keep the components.
So the components themselves are versioned OK, but the connection
between the component version and the programs in which it was used is
very weak if not to say non-existing....
The technique described above for the sources cannot be used either
because we have to switch between projects a lot and it is totally
impractical to have to rebuild the component palette on each project
switch...


/Bo
(Bo Berglund, developer in Sweden)



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