[Top][All Lists]

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

CVS modules and checkouts/updates

From: Duncan Sommerville
Subject: CVS modules and checkouts/updates
Date: Tue, 30 Oct 2001 13:43:35 +0000


So far I have a "modules" file in the following format:

  all       -a  Top
  proj1     -a  SOURCE_A SOURCE_C
  proj2     -a  SOURCE_B SOURCE_C

  SOURCE_A  -a  Top/SourceA
  SOURCE_B  -a  Top/SourceB
  SOURCE_C  -a  Top/SourceC

This appears to works fine - when I attempt a "cvs co proj1" I get the 
following tree:


However, if I now perform an "update" at the top level, I get *everything* 
dragged out of the repository - I end up with the following tree:

    SourceB  <-- new bit

In retrospect this is to be expected, but it's not what I want. Ideally I would 
like to be able to checkout a *project*, and perform updates on the *project* 
tree reguarly and using a single, recursive command.

The only way I can see to achieve this at the moment is via multiple "update" 
commands, one per directory:

  cd Top
  update SourceA
  update SourceC

What I really need is to be able to perform an "update" based on the module 
name, rather than specific directories. I have a suspecion that something like 
this can be achieved using "ampersand modules", but I'm having trouble getting 
to grips with this...

Any help much appreciated.

Many thanks,
Duncan Sommerville.

Do You Yahoo!?
Get your free address at

reply via email to

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