Thanks for the response, James. What is lump? Is it a CVS thing or does it rely on the development environment. Also, can you give me any pointers on what to search for as I do not yet know the correct terminology - I either get millions of hits or none.
Thanks, Ian. "James Youngman" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > "Ian Davies" <[EMAIL PROTECTED]> writes: > > > I am a newly appointed Software Development Manager and am trying to bring > > order to a previously chaotic system. CVS is key to my approach. > > > > I can version the source code of a project and the source code of a shared > > library with CVS separately without problems. What I would like to know is > > if there is any way to tie the two together so that I can regress to > > previous versions of a project that may only work with a previous version of > > a shared library. > > Put the two things in two separate modules, and tie them together in > the modules file like this :- > > lump: &projcode &sharedlib > > Obviously you will be able to provide more descriptive module names. > You can then associate mutually-compatible versions of the two things > by tagging the "lump" module. > > Consult the mailing list archive for more detailed discussion of these > issues - it comes up regularly. > > -- > James Youngman > Manchester, UK. +44 161 226 7339 > PGP (GPG) key ID for <[EMAIL PROTECTED]> is 64A95EE5 (F1B83152). > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
