bzr-windows team mailing list archive

["Dave Murray" <irongut@xxxxxxxxxxxxxxxxxxxx>]

Seems I failed to send this to the list last week. I must have needed more
coffee. ;)

-----Original Message-----
> From: Ian Clatworthy
> Sent: 06 August 2009 06:25
> Subject: [Bzr-windows] [RFI] Windows packaging/installers
>
>
> * OS version: XP vs Vista vs 7 vs 2003, etc.
> * 32 vs 64 bit
> * multiple languages
> * different audiences: gui vs command line as preferred interface
> * bundled documentation format: Windows Help vs HTML vs PDF
> * admin rights: some users will have them and others may not

Separate installers may be required for 32 bit and 64 bit. I'd split
installers by architecture and have install options for Command Line Only,
Typical, Complete and Custom.

The old style Windows Help was killed off in Vista and I'm told HTML Help
(*.chm) is deprecated but can't find confirmation atm. Microsoft's current
preferred option is Document Explorer and anyone who has had the misfortune
to use it will tell you it is awful. So for documentation I'd go with a PDF
and shortcut links to the online docs in the Start Menu.

> * bundled python vs not
> * cygwin vs standard shell

Python, QT and any other necessary libraries must be bundled as most Windows
users will not have them already. Please don't install cygwin unless
unavoidable.

> Also, what do we bundle vs install separately:
>
> * plugins?
> * GUI apps: TortoiseBzr, Explorer or both?
> * 3rd-party tools? (e.g. for ssh, 3-way GUI merging, etc.)

I find TBzr slow, buggy and annoying. Explorer is faster and better. I'd
include Explorer in the default Typical install and have TBzr available as a
custom install option for users that want it. QBzr and the plugins that are
in the installer atm should also be in the Typical install.

It might be useful to include plugins for Eclipse and Visual Studio but they
will increase the size of the installer and many users will not need or want
them. Personally I'd prefer if they weren't included but if they are then
they should be part of the Custom install.

> (d) For hard-code command line folk and server-only usage, a "core"
> installer is offered. This bundle might be called something like "Bazaar
> Core x.y" or "Bazaar CLI x.y" and might contain ...
>
>  * core bzr
>  * Python
>  * any required 3rd-party tools for networking via ssh

I'd include this as an option in the main installer. If a lot of people are
asking for this as a separate product then maybe it should be the third,
harder to find option you mentioned in your paragraph about the number of
installers.

That's my initial thoughts,
Dave.


Dave Murray
Glasgow, Scotland
irongut@xxxxxxxxxxxxxxxxxxxx