September 2009 - Installer-dev

Re: Never upgrade. Always install
by Justin Williams 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com - j On Sep 2, 2009, at 10:53 AM, Nick Peelman wrote: Howard brings up an interesting question...what else are you installing that makes an installer necessary? I assume you're dumping files into /Library or a Kext or something? -nick On Wed, Sep 2, 2009 at 10:33 AM, Justin Williams<justin(a)secondgearsoftware.com> wrote: Hi, Any help would be appreciated. This email sent to nick(a)peelman.us -- Nick Peelman peelman(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… It's a metapackage that contains an application file and another subpackage that installs some config files and certificates into the Library folder. We build each package on the fly using a set of scripts, because the subpackage's contents is unique to each user. Before I got around this issue by just trashing the receipts files in / Library/Receipts/ but with the transition away from those, I haven't found a reliable way to accomplish it in Leopard & Snow Leopard. I am running into an issue with my Installer where many times it will determine that the user should be upgrading their package rather than installing fresh. When this happens, files that are missing (usually the application bundle that should go to /Applications) is not installed. I'd prefer to set my package to never have the option to upgrade and to just always install/overwrite the existing file on the user's Mac. I thought I could do this by adding the "pkgutil --forget net.secondgear.mybinary" command to my postinstall script to remove it from the receipts database, but it doesn't seem to make a difference. What's the preferred method to handle something like this? I was hoping there would be a magic button I could click in PackageMaker, but sadly, it didn't seem to exist. - Justin Williams http://secondgearsoftware.com/ - Check out Today: snapshot view of your daily iCal agenda <http://secondgearsoftware.com/today/> - _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/nick %40peelman.us This email sent to site_archiver(a)lists.apple.com

1 0

Re: Never upgrade. Always install
by Howard Moon 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com -Howard On Sep 2, 2009, at 7:33 AM, Justin Williams wrote: Hi, Any help would be appreciated. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Unfortunately, the whole Installer.app design sucks in this regard, as far as I'm concerned. The "pkgutil --forget" command looks like that's a way to clear the entries from the installed packages database, but the man page for it explicitly says to NOT use it in an installer script. (Just a guess, but perhaps it isn't actually updated until *after* your postinstall script runs?) I have not yet been able to create an installer (using either PackageMaker or Iceberg) that meets our needs, so I'm using VISE-X, which has much greater flexibility and control. Unfortunately, it has a license fee that might make it out of reach for many smaller developers. One possible solution might be to have the user drag a folder containing your software to the Applications folder in order to install, instead of running an installer at all. Then, when run, your software might use some method to detect that it's the first time it's being run, and copy support files from a (possibly hidden) sub-folder to where they need to reside. Just a thought... I am running into an issue with my Installer where many times it will determine that the user should be upgrading their package rather than installing fresh. When this happens, files that are missing (usually the application bundle that should go to / Applications) is not installed. I'd prefer to set my package to never have the option to upgrade and to just always install/overwrite the existing file on the user's Mac. I thought I could do this by adding the "pkgutil -- forget net.secondgear.mybinary" command to my postinstall script to remove it from the receipts database, but it doesn't seem to make a difference. What's the preferred method to handle something like this? I was hoping there would be a magic button I could click in PackageMaker, but sadly, it didn't seem to exist. - Justin Williams http://secondgearsoftware.com/ - Check out Today: snapshot view of your daily iCal agenda <http:// secondgearsoftware.com/today/> - _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/howard% 40antarestech.com This email sent to howard(a)antarestech.com This email sent to site_archiver(a)lists.apple.com

1 0

Never upgrade. Always install
by Justin Williams 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi, Any help would be appreciated. I am running into an issue with my Installer where many times it will determine that the user should be upgrading their package rather than installing fresh. When this happens, files that are missing (usually the application bundle that should go to /Applications) is not installed. I'd prefer to set my package to never have the option to upgrade and to just always install/overwrite the existing file on the user's Mac. I thought I could do this by adding the "pkgutil --forget net.secondgear.mybinary" command to my postinstall script to remove it from the receipts database, but it doesn't seem to make a difference. What's the preferred method to handle something like this? I was hoping there would be a magic button I could click in PackageMaker, but sadly, it didn't seem to exist. - Justin Williams http://secondgearsoftware.com/ - Check out Today: snapshot view of your daily iCal agenda <http://secondgearsoftware.com/today/ > - _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0