Been very busy working on Install the last few days adding a few powerful new features:
Ability to specify multiple installation configurations, each tailored for a particular version (or range of versions) of Mac OS X
Ability to add or remove login items Ability to execute shell scripts, with or without root privileges, as part of "preflight" or "postflight" installation phases Ability to execute shell scripts, again with or without root privileges, and then act on the basis of the exit code from the script No limits on which shell you use (Bash, Perl etc) Can pass arguments to the shell scripts New Item in the Install Application menu to take you to the Install website Lots of internal changes to make the code more extensible and flexible, preparing the way for a new kind of license (a Framework+Binary license) so that developers can customize the installer even further by adding their own subclasses; the new license will be offered as an alternative to the existing Binary-Only and Full-Source licenses Much-improved "Finish" install step, allowing more complicated post-install actions; it is now possible to specify with much more flexibility which files to open and with what applications Ongoing code-auditing to tighten up the code and make it more robust; I haven't found any memory leaks or bugs yet, but I have been making minor adjustments to the code which make it more "future-proof" As part of the above, I've developed some new exception macros to make working with exceptions easier under both the old and the new-style exception models Much more that I can't remember right now... Looks like it's going to be a ripper of a release, and it will enable me to finally release another product I have waiting in the wings, but for which I didn't yet have an installer that could do the necessary bits and pieces to get it deployed...
It's important to remember that I developed Install because I needed a tool to deploy Synergy. I was getting overwhelmed with questions about how to install it (even though it is a simple prefPane).
It's been a highly valuable experience because in writing the program I have created code that has been rolled directly into GetSmart Pro, Synergy Advance and WinHex.
And there's plenty of useful stuff in Install that I can leverage elsewhere: the ability to run stuff with root privileges, the ability to run shell scripts, code for adding and removing login items etc.
Install 1.1 came out last week, and yesterday Install 1.1.1. Version 1.1.2 is already in the pipeline.
To answer your question: yes, I'm not the only developer using Install, although I never expect to license a huge number of copies and I don't think Install will ever "pay the rent" for me. Perhaps once more developers start to see Install being used for deploying software they'll want to license it and thus avoid "reinventing the wheel" when it comes to installing their own software. Compared to the competition, Install is very competitively priced.
But in the case of this application, it's definitely about much more than just the money...
How about giving free licences of Install to freeware app developers?
Instead of keeping separate progress logs for each topic I think I'll just keep one single progress log for all of them. I am putting a lot of work into frameworks that get used by more than one app so it makes some sense to combine the logs. See the new combined log here: