Can't handle different paths in modules
Brought to you by:
adamkennedy
Menu
▾
▴
#17 Can't handle different paths in modules
Assume the following folder structure in CVS:
lib
a
b
project
a
b
and the following module definition:
a -a lib/a project/a
b -a lib/b project/b
Setup a module in cvsmonitor and checkout. You get
CVS errors like
cvs server: existing repository /project/a does not
match /lib/a
cvs server: ignoring module lib/a
Logged In: YES
user_id=153576
Interesting.
CVS Monitor interacts with cvs by passing commands though
to the cvs client installed on the system.
The checkout command it generates generally looks
something like this.
cvs -d $cvsroot -Q checkout -r 1.1 -d $directory $modulename
Can you see something here that would cause your checkout
to fail? Is there an option you would normally have to
specifically set?
Logged In: YES
user_id=661034
This CVS command fails on the described structure. If you
remove the -d $directory parameter, it works fine.
Logged In: YES
user_id=874180
The case I tried (with 0.6.2) looks like this:
project_part project/part
project_rest -a !project/part project
This splits checkouts by subdirectory, which is useful if (as in
our project) many of the authors only work on specific
subdirectories.
CVSMonitor works fine on the first definition, but in the second
definition, it ignores the -a !project/part part.
Logged In: NO
Does it fix yet ?