Re: Flat and hierarchical mirrors of repository

[Russ Tremain]

if everyone uses checkout to update, your design will work okay.
see the cederqvist manual on the difference between checkout
and update.
-Russ


At 4:50 PM -0700 5/1/01, Brian Jung wrote:
>Hi,
>
>       I'm a newbie setting up CVS locally for a group of
>designers who are used to writing code in a "flat" directory
>structure, e.g., src/*.c. Most of their tools assume this flat
>structure. As Murphy's law would have it, other groups we are working
>with prefer the hierarchical tree structure, e.g., moduleA/src/A*.src,
>moduleB/src/B*.c, etc., for their code. My goal is to be able to
>satisfy both crowds.
>
>       Starting with a "flat" repository structure, I can checkout
>a flat mirror (duh). Using the "modules" file in CVSROOT (ampersand),
>I can create subdirectories which can be checked out in local
>directories. However, a global update fills each subdirectory's src
>directory with all the *.src files. I assume I'll have to create a
>script for "update" when I'm doing it heirarchically that goes down
>each subdirectory (to my limit specified in "modules") and do a
>'checkout module'.
>
>       Do any of you have experience with this sort of thing? I
>realize it may be a newbie question and I couldn't find anything with
>my search of the archives. Any suggestions you have, based on your
>insight or experience, I would appreciate.
>
>       I may need to convince my local designers to break their
>code into modules with hierarchy and just make links to a flat
>directory. Or is it fairly straightforward to start with a
>hierarchical repository and create a "flat" mirror (without any
>links)?
>
>Thanks,
>       Brian Jung
>
>_______________________________________________
>Info-cvs mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/info-cvs