← Back to team overview

bzr-windows team mailing list archive

Using buildout to install dependency eggs for installer

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi All

I've started making a change to the bzr-windows-installer scripts so
that it downloads and installs, using buildout, most of the dependencies
one needs to build the windows installers.

Dependencies include:
jinja2
PyCrypto
paramiko
Pyrex/Cython
cogapp
docutils
pyreadline
pygments
testtools
sphinx

I'd like to add PyEnchant at some stage, to add spell checking in
qcommit (https://bugs.launchpad.net/bzr-windows-installers/+bug/651792)

py2exe, pywin32, and pyqt will probably still have to be manually installed.

This will allow us to define the versions of the dependencies used. It
will us to have different versions for different release series.

I'm looking at a way to make buildout to cache what it downloads. What I
have to figure out is how to make it possible for one to configure the
cache location. I think I would make the config file path
%APPDATA%\bazaar\2.0\installer-build.conf. If no config file exists, the
cache dir will default to
%APPDATA%\bazaar\2.0\installer-buildout-chache. This config file could
also be used to config options currently passed to build.py as args.

I'm hoping this will make it easier to setup a build host, and make
builds more consistent.

What do you think?

Gary
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAky9T5AACgkQd/3EdwGKOh3OWgCeLzTQ8HLm6SdTzZyNLAvVqTWG
hHMAoLe+8X7SdzuCdA4OdpGwdMP+wQVk
=Zcah
-----END PGP SIGNATURE-----



Follow ups