Re: multi repository cvs2svn conversion question

Chris Davenport wrote:
> Basically we'd like one SVN repository containing multiple projects
> (code bases) - as this will mirror our CVS setup. Is there an issue with
> having Svn set up this way?

No, it is not a problem and is one of the two standard repository
layouts recommended by the Subversion book [1].

> SVN/Ecommerce
>    --------project1
>    --------project2
> 
> Currently we have two CVS repositories containing multiple projects
> each.
> 
> 
> If I'm interpreting your last email correctly, we wouldn't have to merge
> the CVS repositories - just include the right pathing in the options
> file.

Correct.

> So looking at the option file piece below - this would convert our
> webstart project in our ecommerce repository which resides in our CVS
> dir. Correct?
> To save space I deleted the sybol transform section of it. I had left
> the defaults on.
> 
> Run_options.add_project(
>    r'/var/spool/CVS/ecommerce/webstart',
>     trunk_path='webstart/trunk',
>     branches_path='webstart/branches',
>     tags_path='webstart/tags',
>     initial_directories=[
>         ],
>     )
> So to also add projects within another repository, I would simply add a
> stanza like the following?  - where It would convert the javazone
> project located in the intranet repository within the same CVS dir as
> the ecommerce repository? 
> 
> Run_options.add_project(
>    r'/var/spool/CVS/intranet/javazone',
>     trunk_path='webstart/trunk',
>     branches_path='webstart/branches',
>     tags_path='webstart/tags',
>     initial_directories=[
>         ],
>     )

This wouldn't work because you have specified the same trunk, branches,
and tags paths as for the first project.  cvs2svn would recognize the
conflict and give an error message.  But I suppose you meant to change
those lines to something like trunk_path='intranet/javazone' etc., which
should be fine.

> And finally my last question deals with ambiguous symbols. After the
> collate symbol pass - the conversion stops and informs me that there are
> a few hundred ambiguous symbols. I have left the default symbol handling
> on along with the default catch-all statement.
> Is there a method that is usually employed in this case to handle these
> as a group- or is it nessicarry to explicitly force each individual
> symbol to be either a branch, tag, symbol. Using the hints file.

You've commented out the "symbol_strategy_rules=" part of most of the
add_project invocations, so it is no wonder that you have lots of
unresolved symbols.  You need some kind of rules for each project,
otherwise cvs2svn has no idea what to do.

The HeuristicStrategyRule() in the default global_symbol_strategy_rules
should resolve all ambiguities in a way that is usually reasonable.

Michael

[1]
http://svnbook.red-bean.com/en/1.5/svn.branchmerge.maint.html#svn.branchmerge.maint.layout
http://svnbook.red-bean.com/en/1.5/svn.reposadmin.planning.html#svn.reposadmin.projects.chooselayout

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2465922

To unsubscribe from this discussion, e-mail: [[email protected]].