Hello!
We plan to convert a large CVS repository (2GB, >100.000 files, >50 commits /
day) to SVN.
The structure of this repository currently looks like
/
project1
project2
...
vendor_sw
whereas "vendor_sw" is assigned to several projects by CVS modules.
In our oppinion, the SVN repository should look like
/
project1
trunk
svn:externals vendor_sw -> ,,/vendor_sw/trunk
tags
branches
project2
...
vendor_sw
trunk
tags
branches
At this point, everything works fine.
The problem is, if we tag or branch (svn copy) a project, the svn:externals
property is copied as well, pointing to the current version of vendor_sw. If
we check it out later on, we get the project at date "tagged" but vendor_sw
at date "today". What we want is to to tag project1, to tag vendor_sw and to
change the target of our external definition to the new vendor_sw tag.
Is there a smart way to handle this problem automatically and transparent to
the user (e.g. by a hook-script)?
Thanks,
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 29 10:05:49 2004