bzr-windows team mailing list archive

[John Arbash Meinel <john@xxxxxxxxxxxxxxxxx>]

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

Alexander Belchenko wrote:
> Vincent Ladeuil пишет:
>>>>>>> "bialix" == Alexander Belchenko <bialix@xxxxxxx> writes:
>> <snip/>
>>
>>     >> 4. Hack and test.
>>
>>     bialix> I think we should extract py2exe-related stuff from bzr.dev
>>     bialix> setup.py into this project. There is about a half of setup.py
>>     bialix> dedicated to py2exe stuff (qbzr/tbzr etc.) It should not be in
>>     bialix> bzr.dev core IMO.
>>
>> +42
> 
> :-D
> 
>> Last time I went into setup.py I got lost :-/
>>
>> On the other hand (from memory) I think that reading that I came
>> across a comment somewhere that setup allows to define more
>> commands, this definitely apply here I think even if it's done in
>> the windows installer project.
> 
> This is not our case.
> 
>>      Vincent

I'm not sure what you mean about "defining more commands". You can
define new targets by creating a Builder class, and adding it to the
list of supported actions, etc. Or you can override a builder class (as
we do with build_ext to have --allow-python-fallbacks.)

If you mean "have qbzr tell setup.py about its dependencies" that was
never done. Though I mentioned it often enough while Mark was trying to
actually create the Windows installer in the first place.

John
=:->

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

iEYEARECAAYFAkqmmiwACgkQJdeBCYSNAAN4QQCdFbJ1ZIqfg40FpiqsaFKiFS7r
qCAAni6+1kUSQHIxc84kNhShOmTSHZzh
=vTC8
-----END PGP SIGNATURE-----