Hacking on svn w/o "cleanup"? Possible?

Part of the hacking guide (and user install guide) as this instruction before building svn:

       #!/bin/sh

       # Take care of libs
       cd /usr/local/lib
       rm -f APRVARS
       rm -f libapr*
       rm -f libexpat*
       rm -f libneon*
       rm -f libsvn*

       # Take care of headers
       cd /usr/local/include
       rm -f apr*
       rm -f svn*
       rm -f neon/*

       # Take care of headers
       cd /usr/local/apache2/lib
       rm -f *

Or in other words it appears as if you can't have a functional copy of svn on your system while
you're hacking on svn? There's got to be a better way; The vast majority of OSS projects cleanly
build in their own build directory w/o attaching themselves to whatever old version is on the
system. The better ones can cleanly have multiple versions installed into separate PREFIXes. This
all makes developing, testing, and ultimately administration much, much easier (seamless upgrades).

Do I really I have to break an existing environment before I can even try to *build* the new
version? So my server is down the entire time it takes to build (assuming it builds)?

Do all svn developers work like this (nuking their system installs of svn before each build attempt)
or is there a saner way in which the build can be isolated to its build directory?

Thanks

-Byron

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 18 21:20:21 2007