[Chandler-dev] Changes to how full builds are done

Mike Taylor bear at code-bear.com
Tue Mar 14 21:57:08 PST 2006


Tonight I've implemented a kinda big change to how full builds are 
done.  The reason for the change is a mix of many small reasons, some 
of which are:

   - setuptools really needs to be installed using the chandler python 
*in* the environment that chandler runs in
   - the full builds should be installing it's test environment in a 
similar way that the quick builds do
   - changes made to external or internal libraries ended up being 
tested immediately (and failing most of the time) instead of when 
released

The crux of the change is that the "install" step that each sub-project 
does now copies the generated debug/release tarball into the downloads 
directory (as specified by CHANDLERARCHIVES) and after all sub-projects 
are done the build then runs make install in the chandler directory.

This means that full builds now install their test environment exactly 
like a quick build and any setuptools related changes now can be made 
to a single location - the chandler/Makefile.

The biggest difference for people who work on external or internal 
projects is that if you want your current updates to be tested in your 
build environment you will need to edit your chandler/Makefile locally 
and have it reference the new version and/or relver - if not you will 
be building the new version but only the released version will be 
installed and tested in the chandler/ directory.

Let me know if anybody has any questions about this change or if you 
just want to beat me with a nerf bat for fun :)

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060315/a6fa1a12/PGP.pgp


More information about the chandler-dev mailing list