[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Common code base for different projects
From: |
Matt Riechers |
Subject: |
Re: Common code base for different projects |
Date: |
Wed, 29 Aug 2001 11:14:00 -0400 |
Arcin Bozkurt - Archie wrote:
>
> Hi all,
>
> I have started a repository which now has files I would like to use in
> other projects (say like the files creating a library). The development
> on these files will definitely continue.
>
> What is the best way to do this in CVS? How can I share this set of
> "common files" between projects?
>
> I wanted to create different modules for different projects. Does this
> suggest that I should move out the common files to another module, such
> that any project ( therefore a module on CVS) based on these files will
> be referring to this common module somwhow??? (how? ) - But it sounds
> inefficient in terms of usability ...
>
> Replicating these files in each module is definitely out of question.
> Cause i have to replicate the change on all modules using these files.
>
> Creating a branch on the old module is not logical ( two different
> projects kept in the same module) Or maybe this is what it should be????????
>
> --
>
> Later there will be more libraries, that will have the same problem
> mentioned above. So it is not only for 1 set of files :(
>
> Any suggesstions on how I should structure my projects under cvs?
>
> Arcin Bozkurt
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
You can put those 'common' files in a seperate module which can be linked in to
the others via the modules file.
-Matt
Re: Common code base for different projects, Paul Sander, 2001/08/29