[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: cvs2svn.py problem with --trunk

From: <kfogel_at_collab.net>
Date: 2003-06-12 23:31:08 CEST

Blair Zajac <blair@orcaware.com> writes:
> I think I see where we're both coming from. You're looking to handle
> branches, tags and trunk. I'm looking for a very simple command line
> saying, import path/to/dir1 from CVS into path/to/dir2 into SVN. I
> thought trunk would specify the entire path/to/dir2, but because it is
> interjected into the result path, it actually looks just to specify
> the name of the "trunk" directory in the path, which I don't think
> many people will change, unless they choose "head".
> So for me, the relevance of --trunk is much reduced.
> I think we need a --prefix option, where the path to the top level
> PROJ is specified.

Yup, good point!

> Some other usage notes:
> 1) If you want to rename PROJ to say PROJ1, you can't do it without
> manually moving the directory i

Or running svndumpfilter (or otherwise tweaking the dumpfile before
pass 5 of cvs2svn.py runs). We haven't got smooth support for that
yet, though there will be options to stop/restart cvs2svn later.

> 2) Finally, with the current usage, if you have PROJa and PROJb in
> your CVS repository and you only want to import one, then there's
> no command line usage to do that. It'll import both.

Just run the tool on PROJa (as though it's the root of a repository).
Oh, but then the trunk|tags|branches paths won't be right.

> I think this behavior is assuming too much of the source CVS
> repository and where it should be imported into the svn repository.
> It should be up to the user to decide where to place the CVS repos
> into the svn repository.


These aren't design decisions, you understand; they're just "No one's
gotten around to implementing those options, because they've been
concentrating on basic functionality."

> > We are taking the top level directories of the CVS repository as the
> > PROJects, and splicing the trunk|tags|branches underneath them.
> Sounds like a bad idea, and its confusing. First, I think its better
> to let the user explicitly decide where the source and destination
> goes. Also, now, I have to figure out that trunk in interjected in
> the path. I'd rather just say,
> cvs2svn.py --prefix dump/my/code/here using/code/from/here
> Much easier on my already taxed brain :)

? These two things are orthogonal, or could be...

Could you write a formal description of what you'd like to see happen?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 13 00:17:23 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.