[Chandler-dev] build changes **please read**

[Andi Vajda]

As Bear just announced, the so-called leopard branch has landed.
What does this mean for developers ?

Depending on the operating system you're running, the Chandler build now uses 
system components whenever possible. This is the case on Mac OS X 10.5 Leopard 
PPC and Intel, Ubuntu Linux 7.04 Feisty and 7.10 Gutsy.

Please wait until the tinderboxes are green until your next svn update. 
However, we welcome your impatience and your help in working out the kinks if 
you update before :)

If you are on any of the above operating systems, after your next 'svn update' 
please remove all previously downloaded archives and your release and debug 
binary trees. Old archives may interfere with these new build flavors as we 
haven't incremented all the revision numbers (soooo many builds to do) and may 
not be compatible (for instance, python compile flags or 
MACOSX_DEPLOYMENT_TARGET differences would be in the way).

If you are not on any of the above operating systems, the build is still as 
big as before, after your next 'svn update' just run 'make install' to get the 
refreshed modules such as Berkeley DB, PyLucene, chandlerdb and others (?).

More specifically:
   - on Leopard, we're now using system python, system setuptools, system java
     and system readline.
   - on Gutsy, we're now using system python, system readline, system openssl,
     system icu, system docutils
   - on Feisty, same as Gutsy except for openssl which we still build

Bear added a bunch of new tinderboxes to accomodate all these new build 
flavors. Whenever a module from external/internal needs rebuilding, please be 
patient or be ready to manually build and upload up to 14 flavors.

Andi..