On Jan 13, 2005, at 12:00, Nick Matsakis wrote:
On Thu, 13 Jan 2005, Bob Ippolito wrote:
Click-through is pretty standard with an installer package, I'd go ahead and do it.
Why? Does it indemnify anyone if someone uses appscript to run a nuclear
sub? No one reads that stuff anyway.
I'll usually glimpse at the top to see which license it is. If I want a hassle-free install, I use installer from the command line.
I would install them automatically. If they are on the disk image, people will run them before installing, and they will not work due to missing dependencies.
These apps are faceless background apps that help speed appscript but are
not required for it to run properly.
Even more reason to have them installed behind the scenes. The point is that if you put applications on the disk image, people will click on them and expect them to do something. They won't, so there is no reason to have them out there.
Are you using py2app's bdist_mpkg to build this package or are you doing it by hand?
I'm using Apple's PackageMaker tool.
Why? bdist_mpkg a lot of this correctly and automatically. You should at least use bdist_mpkg to make easy packages out of the installable-by-distutils stuff. Since you are not the author, it might make sense to do the documentation and examples by hand rather than putting in the effort to subclass the bdist_mpkg command and add those schemes (see py2app or PyObjC's setup.py for examples).
If you do use bdist_mpkg, use it from trunk, I made some enhancements.
-bob
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
