On Jan 12, 2007, at 17:04, Mark Bardsley wrote:
> Robert Ioiart wrote:
>> I made some external definition for a directory in my repository
>> pointing to another project(a release) in the
>> same repository. Then I dumped the repository and moved it to
>> another machine. The checkout on the new
>> repostitory failed because the external definition still pointed
>> to the URL in the old repository,
>> which did not exist any more.
>> This means, that after moving a repository with external
>> defintions, projects with external definitions are unusable.
>
> How about doing a checkout without externals (--ignore-externals)
> then editing the externals definitions in that working copy?
Ok, that takes care of HEAD. What about all the other revisions?
What Robert seems to be asking for, with good reason, is a way to
change the past. This runs counter to svn's fundamental assumptions,
so it's little wonder that implementing this requires a rather
hackish search-and-replace on the dumpfile.
We'll be faced with the same issue at my place of work shortly. Our
sources are in Eclipse projects that are checked in, but we have
separate maven build projects, which reference the required sources
via externals. We're currently hosting our sources on a server within
the team, but now there's a company-wide SVN server. At some point
we'll have to migrate our stuff, which means we'll need to either
practice some aggressive historical revisionism WRT svn:externals, or
we'll have to keep hosting a read-only copy of the repository on our
team server indefinitely.
// ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 12 17:14:35 2007