Hi,
I'm trying to set up a CVS repository for a small group of engineers. We have
a project that is logically divided up in to subprojects, so I'd like to set
up the directory structure something like this:
project/
lib1/
lib2/
program1/
program2/
etc...
Each subdirectory will be "owned" by one developer. The other subdirectories
will have dependencies on each other, ie, it is important that the contents of
lib1, program2, etc, compile and "work" for the developer of program1. I was
thinking of using branches for this. Each subdirectory has a "private"
branch, which the developers use for daily checkins. Then, when it is in a
"working" state, the developer releases it to the other developers by doing a
merge. Then, he reforks the main branch and starts again. Here's my problem:
I need this to be easily scriptable. Each developer shouldn't have to become
a CVS guru, or even have to type more than one or two commands to do the
merge/branch. I'd like to keep the branch names simple, such as "private" or
"lib1-private" or "scott-private" - therefore, its not easy to just make a new
branch (I can only seem to have uniquely named branches - is there a way to
"close" a branch and then start a new one with the same name?) Any ideas?
Thanks,
Scott
--
Scott Lipcon [EMAIL PROTECTED]
Software Engineer http://www.cidera.com/
Cidera, Inc 301.598.0500 x4768
