Re: How should I deal with this CVS to Subversion migration issue (and how is this done the Subversion way?)

Hello!

Murli Varadachari schrieb:
> Have looked at this issue for some time now, I found the the solution that
> worked best (atleast in my situation) was to create empty directories in
> place of the symlinks and then use "svn switch" to point these directories
> to the actual component locations.

Another possibility would be using SVK instead of Subversion client. SVK
has the nice "view" feature which allows the definition of a working
copy structure independend of the repository structure.

Unfortunately most Subversion clients like TortoiseSVN or eSVN can't be
used for SVK working copies.

I don't know if the view feature implemented in SVK 2.0.1 will be stable
enough for production purposes. SVK 2.0.0 had problems with views.

Regards
Andreas Schweigstill

-- 
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org