bzr-mac team mailing list archive

[Jean-Francois Roy <bahamut@xxxxxxxxxxxx>]

This is my final Bazaar 2.0.0 distribution for Snow Leopard.

http://www.devklog.net/bazaar/Bazaar2.0.0.pkg

It includes the following packages:

- bzr 2.0.0
- bzrtools 2.0.1
- bzr-email 0.0.1
- bzr-keychain 0.1
- bzr-rewrite 0.5.4
- bzr-svn 1.0
- bzr-upload 1.0dev
- bzr-xmloutput 0.8.5
- subvertpy 0.6.9

Screenshot of the installer showing the introduction text:
http://www.devklog.net/bazaar/bazaar_installer.png

The ReadMe:
http://www.devklog.net/bazaar/ReadMe.html

I do not believe I can upload the file to the official download site  
nor update the Mac OS X downloads page, so someone else will have to  
do that.

I've pushed my infrastructure for building the distribution on  
lp:~jeanfrancois.roy/+junk/SnowLeopard-package. It is *very* rough at  
the moment.

The basic operating principle is to place all the desired packages  
into src/ and run build.py. build.py will stage each individual  
package into a "destination root" inside the packages directory, and  
then run PackageMaker using a pre-made PackageMaker document which has  
been created to match the output of build.py.

Obviously, this works fine if the same set of files are produced, but  
will break if files are added or removed (because of an update or  
because a new package was added). Therefore, moving forward, build.py  
will need to update some of the PackageMaker document's internal files  
to fully automate the building process. I have a scaffold for a  
"PackageMakerDocument" class in the script to that end, but it is  
barely off the ground.

I'm not sure how this compares to what Guillermo has already, but from  
what he mentioned in the draft distribution thread, he has a more  
complex but more automated workflow. In any case, the destination root  
model makes it easy to use Package Maker manually to build the  
distribution.

Jean-Francois Roy