On Mar 31, 2006, at 1:21 PM, Wayne Linder wrote: We have a Distribution Project to install an app, Kexts, and a slew o' stuff into the System, Since one of the things is a new file system, we need it to be limited to 10.4, obviously. The problem is this; when someone tries to launch the installer (ignoring the System Requirements and the ReadMe - how strange) in 10.3, Installer launches with no interface. Since 10.3 ignores the Distribution.dist - and any scripts inside, putting in a VolumeCheck is worthless. I do have an InstallerCheck package in the bundle, and it works fine by itself, but when rolled into the metapackage, doesn't seem to have any effect - most likely because the distribution project is 10.4-only. So, it won't launch in 10.3 to display a message that it can't run - catch 22!
Any ideas on how I can tell the user in 10.3 that they can't install?
10.3 Installer has NO KNOWLEDGE of distribution scripts AT ALL. It literally has no idea they are there.
If you put an installation check script into a package, and put that into the metapackage, you MUST make sure that that package is marked REQUIRED in the Info.plist.
Normally, I'd pick one of the packages (or all of them) and have an InstallationCheck that just says #!/usr/bin/perl
# This script only runs on 10.4 systems, so it can always... exit(( 1 << 6 ) | ( 1 << 5 ) | 16);
InstallationCheck.strings says: "16" = "This software requires Mac OS X 10.4 or newer.";
|