Re: [SVN-MIGRATION] Argh!

Travis Swicegood wrote:
> That's actually a *really* bad idea.  There are a lot of third-party
> tools that rely on the standard SVN repository layout that this will
> break.  It would be much easier to write a few simple scripts to handle
> checkouts of multiple repositories or as Hannes pointed out use
> svn:externals with a few repositories such as pecl-all might also be a
> good solution.

What sort of 3rd party tools?  I'm more worried about our own 1st party
tools that are currently completely broken because of this structure.

But yes, if this can be fixed via some svn:externals magic ok.

We also have to find a good way to do what cvsup did for our cvs
repository.  rsync.php.net fetches most of the repository and keeps a
copy for serving up via rsync to mirror sites and all sorts of tools.
That is obviously broken right now.  Watching the pathetic performance
of svn over http last night, that is definitely not an option.  We need
an efficient way to clone the repository.  Step 1 might be to get
svnserve set up and perhaps that would be quick enough to let us do a
straight periodic update from the rsync server.

-Rasmus