I work with two different applications in CVS. One has a module
specification that uses aliases to specify several subsystems. The other
uses the "ampersand" rule. So when I do a checkout of the first system,
that just creates subdirectories in the current directory to represent the
various subsystems. When I do a checkout of the second system, that creates
a top-level directory in the current directory, and creates subdirectories
in that directory.
For example purposes, call the first system "foo" and the second system
"bar". There are subdirectories "foo1", "foo2", "foo3", "bar1", "bar2", and
"bar3". The modules file entries for these might look like this:
---------------------------------------
# Foo system
foo1 -d foo1 some/complex/path
foo2 -d foo2 some/other/complex/path
foo3 -d foo3 some/where/else
foo -a foo1 foo2 foo3
# Bar system
bar1 -d bar1 some/miscellaneous/place
bar2 -d bar2 some/other/strange/place
bar3 -d bar3 some/place/else
bar &bar1 &bar2 &bar3
----------------------------------------
We've been using "cvs rtag" to make version tags for the first system, and
I'm just starting to set up version tags for the second system. For the
first system, we do "cvs rtag FOOKIT_01 foo". This works fine.
For the second system, I tried " cvs rtag BARKIT_01 bar", and it gave me the
following:
cvs server: cannot make path to bar: Permission denied
cvs server: cannot chdir to bar: No such file or directory
What am I doing wrong, or what information do I need to track this down?
============================================================================
===
David M. Karr ; [EMAIL PROTECTED] ; AT&T Wireless & Best Consulting
Software Engineer ; Java/CORBA/Unix/C++/X ; TekMetrics CJP (4/20/1999)
