-
Bug
-
Resolution: Duplicate
-
Trivial
-
None
-
Platform: All, OS: All
The cvs command generated includes the -d workspace option but this fails with
our module definitions, which look like this (in the CVSROOT/modules):
main -a products/main products/buildsystem products/etc
In this case, you get cvs errors like
cvs checkout: existing repository /usr/cvs/products/main does not match
/usr/cvs/products/buildsystem
...
The solution turns out to be adding the -N option. When combined with -d it
indicates that the directory path should not be shortened to eliminate empty
parent directories, which in this case would be "products." For some reason
this also eliminates the error.
So perhaps you could add that option to the CVS command or otherwise add an
option to specify it, like a checkbox with "checkout modules without empty
parent directories".
Am using cvs version 1.11.17
- duplicates
-
-
- Resolved
-
[JENKINS-337] Unable to checkout aliased modules
bkayser
added a comment - Sorry, there is no further action on this (unless you want to improve the
label) but I can't seem to close it.
bkayser
added a comment - Sorry, there is no further action on this (unless you want to improve the
label) but I can't seem to close it. I also think this option should be labelled better. The docs imply that the only
reason you would want to use it is for B/C if you were originally running an old
Hudson release. This is not true.
bkayser
added a comment - Note that the backward compatibility option works for the checkout but falls
over in the changelog. I submitted a separate bug on that, bug 427, and renamed
the summary to reflect the request to change the label on the legacy option.
In bug 427 I suggest a slightly different implementation of the legacy option
which uses the cvs -Nd combination to check out the full path, instead of
omitting the -d option.
Anyhow, here are some suggestions for labels:
"Keep full module path on checkout."
"Don't shorten module paths on checkout."
"Don't use -d modulename option on checkout."
I also recommend changing the help to add additionally: "This option is also
necessary when using CVS module aliases (the -a option)."
bkayser
added a comment - Note that the backward compatibility option works for the checkout but falls
over in the changelog. I submitted a separate bug on that, bug 427, and renamed
the summary to reflect the request to change the label on the legacy option.
In bug 427 I suggest a slightly different implementation of the legacy option
which uses the cvs -Nd combination to check out the full path, instead of
omitting the -d option.
Anyhow, here are some suggestions for labels:
"Keep full module path on checkout."
"Don't shorten module paths on checkout."
"Don't use -d modulename option on checkout."
I also recommend changing the help to add additionally: "This option is also
necessary when using CVS module aliases (the -a option)." Issue #427 is the same issue.
-
-
- This issue has been marked as a duplicate of 427 ***
-
Well it seems that setting the option to preserve backward compatibility solves
the problem. This sets an attribute called "flatten" to false.
I'm surprised the option wasn't labeled better to indicate what it actually
does.
Sorry for the noise. Awesome product. I'll close this now.