site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=Z6SmCIEddHP562Gp2oNBGoNhPvle0+jHLlQIeYhJ0bQ=; b=bSFaqSbfU4CkpfFy4CwghDuViLCjW6TddEQ+hjlD6qkiTR6wZ5nsaVXRGilVTmWnck N5Dy4SYZTSNTDXcmjwHqezTs8hG+ket3oVFhqxgO5UQw83WQwIPzixoDOyg7iTlnrLkF ujqzda/ydeLWZOlW8K2FC+PMmUX/aCn4IpPBE= On Dec 22, 2011, at 3:15 PM, Howard Moon wrote:

On Dec 22, 2011, at 12:43 PM, Ryan McGann wrote:

...

What happens if the user upgrades their machine from 10.6 to 10.7, after your (10.6) app is installed? You'll need to handle that scenario, gracefully I might add.

-- Ryan

Hmmm, interesting point! But... how has this scenario traditionally been handled? Certainly there are apps out there that have become obsolete after an OS update, right? The apps can't detect the update as it occurs, and may simply fail when executed. Not sure how one fails gracefully in such a case. Is there an Apple "standard" for such things?

Thanks, Howard

Some people have gone the other way, and merge the two apps into the same bundle, and then make a third 'loader' app which is when gets initially run, which then loads and runs the real app based on which OS is running. This makes the app bundle larger, but handles the upgrade/install problem you are having. Eli _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com