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

Custom protocoll for svn:external.

From: Sandberg Per <per.sandberg_at_saabgroup.com>
Date: 2007-04-04 17:15:07 CEST

All,
I got a problem wher we got lots of our system in a legacy VC system and
I want to use SVN as master VC system in the future.
So one solution to do the migration over tim is as i see to make it
possible to used a mixed system where
The svn external tag uses a custom protocoll and it is up to the user to
provide an exectabl that handles that uri som sample:

svn:external
component_a [CUSTOM]://some_path:and:more:/component_a/rev-1.1
component_b [CUSTOM]://some_path:and:more:/component_b/rev-1
component_c [CUSTOM]://some_path:and:more2:/component_c/rev-2.1

And the have svn to do som thing like this:
   CUSTOM "component_a" "//some_path:and:more:/component_a/rev-1.1"
   CUSTOM "component_a" "//some_path:and:more:/component_b/rev-1"
   CUSTOM "component_a" "//some_path:and:mores:/component_c/rev-2.1"

Where CUSTOM is a command in path and the command is spawned for each
line.

------------------------------------------------------------------------
-----------------------------------------
Is ther anyone that got similar ideas thougths on how to migrate slowly
and use differnet VC systems at the same time.

/Per
Received on Wed Apr 4 17:15:37 2007

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