bzr-windows team mailing list archive

[Gary van der Merwe <garyvdm@xxxxxxxxx>]

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

On 11/10/2010 20:40, Gary van der Merwe wrote:
> On 11/10/2010 19:39, Maritza Mendez wrote:
>> Right!  It looks like the Windows builds are currently being done with
>> the free VS2008 and in the EC2 cloud.  This adds complexity to what is
>> already a pretty complicated build, even for x32.  I'm in the process
>> (slow, in my spare time) of getting the x32 build going (on my own
>> hardware and retail VS2008) with the plan being to then move on to x64.
> 
> Correction: The ec2 build host has the paid for version of vs.
> 
> 
>> Question: Does the Windows package of bzr really need to support more
>> than one version of python?  I'm inclined to build bzr+friends for
>> python 2.6 or 2.7 and drop the legacy.  I especially want to drop
>> MinGW.  I have the 32- and 64-bit MinGW compilers both working, but
>> again it's extra work which does not seem to add value now that we have
>> python 2.6 which I gather is built using VS200x anyway.
> 
> 
> We build python installers for different versions, but these just
> install site-packages in an existing python installation, and so the
> architecture support is base on the python installation that you install
> into.
> 
> These python installers are really easy to get building. The thing that
> makes it difficult so build the stand alone py2exe installer, with all
> the plugins, is tortoisebzr. It would be great to make it possible to
> disable building components (such as tortoisebzr, or the python
> installers.)

Oh silly me, It's easy it is easy to not build 2.4, and 2.5 installers,
by excluding them from --pythons-dir.

Gary

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

iEYEARECAAYFAkyzXPcACgkQd/3EdwGKOh32sACfURphFv/UMBgB5Ats+aQm7G/X
L4QAnRRtv2daM+MK/BuKPBEsmiuHgyX6
=F5xK
-----END PGP SIGNATURE-----