Re: [SVN-MIGRATION] Argh!
| From: | Derick Rethans | Date: | Sun, 12 Jul 2009 09:46:52 +0000 |
| Subject: | Re: [SVN-MIGRATION] Argh! | ||
| References: | 1 2 3 | Groups: | svn.migration |
| Request: | Send a blank email to svn-migration+get-430@lists.php.net to get a copy of this message | ||
On Sat, 11 Jul 2009, Rasmus Lerdorf wrote:
> 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.
svnsync works pretty well for this. I already compiled subservsion for
this 100 year old RH7.3 box and was on the way setting this up when I
read about changing structure again. I can continue this.
regards,
Derick
--
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
twitter: @derickr