Re: how to manage two simular projects?

[Kaz Kylheku]

In article <address@hidden>, Christoph Bayer wrote:
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_0021_01C1A779.055BFAC0
>Content-Type: text/plain;
>       charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>
>Hello everybody,
>
>I want to mangage two very simular projects with cvs:
>They have a big common part and small parts which make
>the projects different.
>
>I would like to have it working like this: If I check-out
>Project one, cvs checks out the common part and the
>the part special for project one. And the same for project two.
>
>And there is the problem that the special parts are not in one
>toplevel directory only, but in some directories somewhere in
>the directory three).

CVS does not support this very well. You should factor out the common
parts into their own module. You can then share it using appropriate
definitions in the modules file.  Ideally, the common parts should form
some kind of unit. If they are code written in a programming language,
maybe they can be made into a library or package, or whatever integration
mechanism your language supports.

It's possible to choose individual files from a module. So you can throw a
bunch of files into one big module and then pick and choose which ones are
used in other modules. There is syntax for doing this in the modules file.
on what depending on what

>I have attached a file with a sample directory structure:

Please don't send attachments to Usenet newsgroups or discussion mailing
lists. Pasting plain text will do just fine.