Repo lay out multiple modules under same tags branches dir
Jess137 <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
Hi,
I need help with the propers settings to create the desired svn dir
structure.
I have multiple cvs projects:
pA
pB
pC
I'd like to convert them into 1 svn with a structure like this:
rep1/trunk/pA
rep1/trunk/pB
rep1/trunk/pC
rep1/tags/<tags>/pA/<subdirs>/...
rep1/tags/<tags>/pB/...
rep1/tags/<tags>/pC/...
rep1/branches/<branchs>/pA/<subdirs>/...
rep1/branches/<branchs>/pB/...
rep1/branches/<branchs>/pC/...
I don't know how to set properly the file configuration to do that. Could
someone help?
I tried this but got not the structure desired:
cvs2svn configuration file:
projects = [
'pA',
'pB',
'pC',
]
for project in projects: # This will run the lines that are tabbed
# Create the default project (using ctx.trunk, ctx.branches, and
ctx.tags):
run_options.add_project(
r'/home/jess/subversion/CVS_REPO/'+project,
trunk_path=('trunk/'+project),
branches_path=('branches/'+project),
tags_path=('tags/'+project),
initial_directories=[
# The project's trunk_path, branches_path, and tags_path
# directories are added to the SVN repository in the project's
# first commit. If you would like additional SVN directories
# to be created in the project's first commit, list them here:
#'releases',
],
...
I ended up with:
rep1/trunk/pA
pB
pC
rep1/tags/pA/<tags>/<subdirs>
/pB/...
/pC/...
rep1/branches/pA/<branches>/<subdirs>
/pB/...
/pC/...
I'd like to have the projects w/in the <branches> subdirectories created
from the <branches> existing in the converted CVS repo.
Thanks in advance for any help,
Jess
--
View this message in context: http://old.nabble.com/Repo-lay-out-multiple-modules-under-same-tags-branches-dir-tp28446197p28446197.html
Sent from the cvs2svn - users mailing list archive at Nabble.com.
------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2602620
To unsubscribe from this discussion, e-mail: [[email protected]].