Re: Sharing a file between to different modules (A dead-horse topic?)

[Greg A. Woods]

[ On Friday, May 31, 2002 at 13:05:12 (-0600), Casey T. Zednick wrote: ]
> Subject: Re: Sharing a file between to different modules (A dead-horse   
> topic?)
>
> Would work, but would not exploit the computers full ability: doing stuff 
> so humans do not have to (The library is under constant development, thus 
> needs to be checked-out and re-built with main project)

On the other hand if you separately release manage your library
(i.e. treat it as a separate product), then you can simultaneously test
each project which uses that library against multiple releases of the
library.

Versioning and release management and all the other aspects of Software
Configuration Management are not about using the computer to do all the
boring stuff -- it's about good engineering and good software hygiene,
etc., which is indeed sometimes quite tedious, but for very good reasons.

> I was hoping to setup it up so when the main module that depends on a 
> another module is checked out, that  the other module would also be checked 
> out too.

You can try to do that with features of the modules file, but 

> That way the dependent code could be modified and checked back 
> in.

You shouldn't be modifying shared code from within a project that uses
that code.  That's what I mean by separately releasing the library and
only using released code in the projects that use the library.

There are many many benefits to treating shared code as a separate product.

-- 
                                                                Greg A. Woods

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