site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Hello All, Is anyone aware of a good work-around for this problem, other than breaking up our metapackage into separate installs? Is there a good way to use InstallationCheck or a preflight script to prevent the user from installing an old version for one of N components? We are using Iceberg, BTW. Many thanks, Monte Benaresh PACE Anti-Piracy On Oct 21, 2010, at 3:55 AM, Stephane Sudre wrote:

Looks like a bug of Installer.app. The only thing you can do is report it to Apple's Bug Reporter system.

On Thu, Oct 21, 2010 at 2:16 AM, Alexander Cohen <alexcohen@toomuchspace.com> wrote:

...

Heres what i've got. I have a metapackage create with PackageMaker 2.0 that contains 4 packages also created with 2.0. The version numbers of all packages and metapackes have been bumped up and the identifiers have not changed. When i run the old metapackage over the new one, it just runs through as an upgrade and installs everything. If i run each of the old packages over the new install, each package wont let me install and says a newer version already exists on disk. This is the right behavior but users wont install like that. So why wont the old metapackage either not replace anything on disk or just tell the user that there is a newer version disk.

---

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/monte%40paceap.com

This email sent to monte@paceap.com

_______________________________________________ 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