← Back to team overview

bzr-mac team mailing list archive

Re: [RFI] OS X packaging/installers

 


* different audiences: gui vs command line as preferred interface

	GUI interface for "default" Mac users, and CLI for code developers.

* bundled documentation format: HTML vs PDF vs Help Viewer

	Help Viewer, use always the OS defaults.

* bundled python vs not? If not, assume which platform version?

GUI interface should work with stock python, and it should not include an installer (aka : drag app from disk image and it is installed).


(c) The recommended installer ought to have everything necessary for a
great experience included. This bundle might be called something like
"Bazaar Desktop x.y" and might contain ...

* Bazaar Explorer
* QBzr
* Qt and PyQt
* Documentation in Help Viewer format. The docs ought to cover the
  core bzr tool + some docs on the GUI tools
* popular plugins (e.g. bzr-svn)
* libraries/binaries supporting those plugins
* core bzr

This installer needs to be available in many languages. If documentation has been localised for a given language, we bundle that instead of or in
addition to the English docs.

Please, do not use an installer for Bazaar Desktop. Just make an app and bundle bzr inside it. There's no reason to make an installer if we can make the app much more appealing without it. They can try without installing it and breaking their OS or opening a Terminal window (remember, .

(g) Everything is up for debate. (a)-(f) are just an *example* of the
sort of input I'm hoping others will provide. While I've used a MacBook Pro laptop for most of the last 3 years, I use Ubuntu on a desktop right
now and under Parallels on OS X whenever I can. So I'm arguably Mac
savvy but a long way from hard core. If you live and breath OS X, your
opinion is 10X more important than mine. :-)

I'm a Mac user for 5 years and we're using bzr for some projects here, but I really do not like the "hey, I need your admin password to install this software because I'm too lazy to read the apple guidelines and use some developer tools to make the app work without a hardcoded path and avoid an installer" idea. Yeas, I know I'm a bit paranoid with the admin password, but OS X is not Windows or GNU/ Linux, we do not need to install apps. We just drop it :)

:: marcelo.alves



Follow ups

References