[MERGE][1.12] setup/build updates for win32 and bzr-svn 0.5.0

[John Arbash Meinel]

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

Jelmer Vernooij wrote:
> Hi John,
> 
> On Wed, Feb 11, 2009 at 10:22:34AM -0600, John Arbash Meinel wrote:
>> The new bzr-svn needs to have subvertpy installed. It is actually a
>> separate package now, so it needs to be included in setup.py (the same
>> way we include PyQT, et al, for qbzr).
> Thanks for looking into this.
> 
>> However, PyQT doesn't change as often as I expect subvertpy to change,
>> so I also updated the build_release.py script. With these changes,
>> build_release.py now stages subvertpy into the build with everything else.
> subvertpy should be rather stable; its current incarnation hasn't
> changed its API for months now - changes have been a Windows-specific fix, 
> some new status codes and more docstrings.
> 
>> --- tools/win32/build_release.py	2009-01-12 18:17:05 +0000
>> +++ tools/win32/build_release.py	2009-02-11 15:45:01 +0000
>> @@ -4,10 +4,11 @@
>>  # When preparing a new release, make sure to set all of these to the latest
>>  # values.
>>  VERSIONS = {
>> -    'bzr': '1.11',
>> -    'qbzr': '0.9.6',
>> -    'bzrtools': '1.11.0',
>> -    'bzr-svn': '0.4.16',
>> +    'bzr': '1.12',
>> +    'qbzr': '0.9.7',
>> +    'bzrtools': '1.12.0',
>> +    'bzr-svn': '0.5.0',
>> +    'subvertpy': '0.6.2',
>>  }
> ^^^ subvertpy is not a plugin, why is this necessary?
> 
> Cheers,
> 
> Jelmer
> 

For the reason I just outlined. I stage 'subvertpy' into the build
directory, rather than assuming it is installed in C:\Python25....

Considering you just released 0.6.2 and have made updates for 0.6.3, I
assume there will at least be *some* development here, and we'll want to
make sure to package whatever the latest version of subvertpy is available.

By making the change here, I can quickly update the build by changing a
single number. Rather than uninstalling subvertpy from the global
python, grabbing the latest, installing it, etc. The build script takes
care of all of that for me.

John
=:->

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

iEYEARECAAYFAkmTBnYACgkQJdeBCYSNAAMASQCfYbtuXQqc7MdS1sqHL6Nujhy/
50IAoK/kZs2GNEvStHQ2tLiTFjZrMhFy
=6F5Q
-----END PGP SIGNATURE-----