> James Knowles writes:
>>
>> I've struggled a bit to figure out how to best set up CVS to handle these. I
>> can create a zillion projects under a single CVSROOT location, but that very
>> quickly gets messy. However, it does have the nice benefit of only one
>> $CVSROOT environment variable.
Which is irrelevant, since a checked-out module 'knows' its CSVROOT, so you
don't see it and it doesn't matter if they differ across projects.
If it's all the same to you, why not keep the hierarchy, where the top few
levels are just for organizational purposes (and eg. would not be visible in
released products).
You can use the CVSROOT/modules file to have aliases and combinations of bits
and pieces at lower levels into new 'checkoutable' configurations.
> Why do you say it gets messy? Pretty much the only reason to consider
> multiple repositories is if you need to have different things in the
> administrative files in $CVSROOT/CVSROOT.
More importantly (in a multi-user enviroment at least) for different access
rights/policies. The way I look at repositories is as a unit of
authorship/authority, where as a module is a unit of logic or (domain)
functionality.
Philip
--
The mail transport agent is not liable for any coffee stains in this message
-----------------------------------------------------------------------------
Philip Lijnzaad, [EMAIL PROTECTED] European Bioinformatics Institute,rm A2-08
+44 (0)1223 49 4639 Wellcome Trust Genome Campus, Hinxton
+44 (0)1223 49 4468 (fax) Cambridgeshire CB10 1SD, GREAT BRITAIN
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
