when changing build/config stuff, always do this first

Yo everyone: if you change part of the configuration/build system,
please make sure to clean out any old installed Subversion libs
*before* you try building with your changes. If you don't do this,
your changes may appear to work fine, when in fact they would fail if
run on a truly pristine system.

This script demonstrates what I mean by "clean out". This is
`/usr/local/cleanup.sh' on my system. It cleans out the Subversion
libs (and the installed httpd-2.0 libs, since I'm often reinstalling
that too):

   #!/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 *

When someone reports a configuration bug and you're trying to
reproduce it, run this first. :-)

The voice of experience,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:49 2006