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

Re: Warning: database schema changes are a-comin'

From: Michael Wood <mwood_at_its.uct.ac.za>
Date: 2003-06-11 17:14:04 CEST

On Wed, Jun 11, 2003 at 11:06:23AM -0400, John Peacock wrote:
> cmpilato@collab.net wrote:
> >I'm sending out this warning a few days in advance so
> >that all you Subversion repos owners are aware -- you have an
> >'svnadmin dump/load' cycle in your near futures.
> Bother. I just get two instances of the All Perl Changes repository built
> and now I have to dump/load. Hmmm, can't be helped, but I do have to find
> the ~3.5GB of space to store the dump. :(

ummm... that's what pipes are for :) All you need is space for two
repositories. Not sure if that helps you though :)

i.e.: svnadmin dump old | svnadmin load new

> >In order to reduce the pain a little, I would highly recommend that
> >you make static builds of 'svn', 'svnadmin', and 'svnlook' based on
> >the current codebase,
> Is this still './configure --disable-shared' and then rename the
> executables before running configure again? I don't see much more
> information in the list archive...

I seem to remember there was also some sort of --enable-all-static
option or something similar. Haven't bothered to use either option yet,

I've just looked at the output of configure --help:
  --enable-all-static Build completely static (standalone) binaries.

So it looks like that's the one to use.

Michael Wood <mwood@its.uct.ac.za>
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 11 17:15:03 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.