bzr-windows team mailing list archive

["Alexander Belchenko" <bialix@xxxxxxx>]

--- Исходное сообщение ---  
От кого: John Arbash Meinel <john@xxxxxxxxxxxxxxxxx>  
Кому: Martin Pool <mbp@xxxxxxxxxxxxx>  
Дата: 14 августа, 16:37:07  
Тема: Re: [Bzr-windows] Difference between windows installers OR standalone vs. python-based again!  
  
  -----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1  
  
Martin Pool wrote:  
> 2009/8/14 Alexander Belchenko <bialix@xxxxxxx>:  
>> I don't said I've heard it from you directly, but I've seen something like  
>> that in Sprint Notes. Can't find the original text though, so I can admit  
>> that may be I have false memory.  
>>  
>  
> I think I remember the note you're talking about, and it was just a  
> poor representation of a conversation along the lines of this thread.  
>  
  
So *I* think that we would be best served by either a network installer,  
or a bundle everything but only install what is necessary installer.  
Either way, it could install Python and then install the extra libraries  
into that.    
Don't forget that in this case you (or other windows maintainer) should build separately for each supported Python version:  
  
* Tortoise bzr binaries  
* bzr-svn binaries  
   
Of course you can limit distribution to 2.5 or 2.6 only. I don't know... For me self-contained bzr.exe is much simpler option.  
  
Also I don't know how it's planned to have all Python libs installers inside one big bzr installer. Python has MSI installer, but almost all other Python libs provides only exe installers.  
  
I'm really don't understand why you think python-based only solution is better for end users. Only because bzr-gtk and/or/xor Loggerhead problems?  
  
  And obviously if you already have Python + PyQt + ... you don't have to  
then re-download everything from scratch if you get the 'lite' installer.  
  
John  
=:->  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1.4.9 (Cygwin)  
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/  
  
iEYEARECAAYFAkqFaIMACgkQJdeBCYSNAAPP9wCgwv3epxYSwOp+arjQg6KcBc26  
eYoAoLs3CNVoCTEstk4wrA1n62fCfseT  
=y542  
-----END PGP SIGNATURE-----