On 8/12/06, Ryan Schmidt <subversion-2006c@ryandesign.com> wrote:
>
>
> On Aug 12, 2006, at 20:38, Mark Clements wrote:
>
> > However, it occurs to me that if we move domains (e.g. to
> > mydomain2.com)
> > then all these old links will be broken! Is there anyway to avoid
> > this,
> > e.g. to use relative links, or to edit historical data after a change
> > (without creating new revisions). I want to be sure that if we
> > need to
> > build Project1 v1.0 in a couple of years (possibly having moved
> > servers)
> > that all the necessary files are still available and are from the
> > correct
> > version.
>
> You are correct, externals will break if the URL to the repository
> changes. I am not aware of a way to avoid this. I do not know if you
> can easily edit it after the fact, for example by editing the output
> of svnadmin dump. Subversion does not support relative paths in
> external definitions yet; it's an open feature request. Suggest that
> if you change URLs, you then visit all projects where you've used
> externals and update the definitions. Also suggest you pick a URL now
> that's unlikely to need to change. (For example, pick a new hostname
> like svn.example.com, even if you're currently hosting it on the same
> machine as other things; this way you can break it off onto a
> separate machine later should you wish to do so.) This also includes
> deciding what server protocol you're going to use.
>
>
Ideally we would like to have the externals point to a relative path or be
able to edit the external at the server if the server moves. But until then,
you can checkout without externals (--ignore-externals), edit the
svn:externals and check-in changes, right?
--
-Hari Kodungallur
SpikeSource Inc.
http://developer.spikesource.com
Received on Sat Aug 12 22:33:20 2006