[Top][All Lists]

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

Re: Organising our Project

From: Greg A. Woods
Subject: Re: Organising our Project
Date: Thu, 6 Sep 2001 21:06:33 -0400 (EDT)

[ On Thursday, September 6, 2001 at 16:11:14 (+0100), Robert Bergs wrote: ]
> Subject: Organising our Project
> I was hoping to use
> branching  on  the  sinatra_core  module  but we cannot pass -r to things in 
> the
> module list.

Nope, you can't..... so go the limits of the CVS "modules" facility.  :-)

> Sorry for the long explanation, but I have two quick questions:
> a) Is this a sensible approach, or is there a better way of using CVS?

I would not call it 100% "sensible", at least not from a larger SCM and
engineering perspective.

You really should be separately managing the common files as a separate
internal product that you install on your build machines (perhaps in
some way such that you can have multiple releases in place
simultaneously).  If they're all compiled source modules (and related
header files) then you'd be installing just the object libraries for
direct linking by the related projects.

>From a software engineering perspective, with a strong leaning towards
good software hygiene, you probably want to define a concrete API for
your common code so that consumers of it (i.e. the other projects) have
a solid well defined set of expectations to work from.  In the OO world
this is called a software contract and it's defined between the
implementer and the user of every object class.

                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>

reply via email to

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