[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: what's the strategy for managing mostly common code with a few proje

From: Pierre Asselin
Subject: Re: what's the strategy for managing mostly common code with a few project specific files?
Date: 15 Nov 2001 15:05:49 -0600

"HEILES,KATRINA (HP-Vancouver,ex1)" <address@hidden> writes:

> I have a set of code that is used by several projects.  Most of
> the code is common, but some are project specific/configuration
> files.  What's the best way to manage this?

Orgarnize each project so that the common files are segregated to a
single directory (or directory tree).  Then set up your modules file
like this:

    common      path/to/the/common/subtree

    proj_A      path/to/project_A &common
    proj_B      path/to/project_b &common

When you check out module "proj_A", your sandbox will look like this:

            the common subtree...

> I'm envisioning that each project will pull the common code from
> a labelled version of the trunk.

I generally put a big README file at the top of proj_A that says
something like this:

    This project needs revision 1.4 of the common subtree.  Before
    building, execute the command

        $ cvs update -rREV_1_4 common

This README file is under revision control like the rest, and you
update it when you port to a higher rev of common/ .  Note that you
won't be able to commit changes to common/ from the proj_A sandbox,
which may be a good thing.

The common/ subtree had better be mature and stable, or you'll soon be
in trouble.  Also, it helps a lot if you can check out, build and
regression-test the common/ submodule by itself, without any files
from an enclosing projet.  CVS will let you check out common by

> Does it makes sense to have the project specific files specified
> differently in a modules file? I'd like projects to be able to pull
> from the same label but still have the ability to have a few files
> not come from that label.

I'm not sure what your first question means, but if you mix tags you
do so at your own risk.  You may find yourself unable to rebuild
proj_A because you forgot what exact combination you were using
under common/ .

Pierre Asselin
Westminster, Colorado

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- - The #1 Newsgroup Service in the World!
-----==  Over 80,000 Newsgroups - 16 Different Servers! =-----

reply via email to

[Prev in Thread] Current Thread [Next in Thread]