Re: Version checking and InstallationCheck
Re: Version checking and InstallationCheck
- Subject: Re: Version checking and InstallationCheck
- From: Stéphane Sudre <email@hidden>
- Date: Tue, 28 Aug 2007 23:53:30 +0200
After being explained that this is in fact a warning in the user
documentation, an educated guess:
InstallationCheck scripts are currently working.
For InstallationCheck not to be supported, this would mean that you
need to use Distribution Scripts because IMHO, you can't rely as much
on Requirements as on an InstallationCheck script. Distribution Scripts
are not supported on Mac OS X < 10.4. So if you have an application
that works on 10.3.9 and later (iTunes still does according to the
Apple web site), it would now require 2 packages. This is not
manageable and it would anyway prevent a bunch of applications from
installing on the upcoming release of Mac OS X due to their current
package format. As an illustration, note how 10.1 format packages are
still working on 10.4.10.
So if you don't bother about your package potentially becoming unusable
in 2 or 3 years, then you _probably_ don't have to worry about
InstallationCheck.
My $0.02
On lundi, août 27, 2007, at 10:33 PM, Stéphane Sudre wrote:
On lundi, août 27, 2007, at 05:56 PM, Dallas Jones wrote:
Hi there -
I want to be able to install one of two packages as part of a
metapackage
depending on whether a file is found. I have edited the packages to
add a
package requirement; one of them will install if the file is found;
the
other will not install if the file is found.
This didn't work - the installation fails if the requirements for
either of
the packages fails.
It looks like I can do what I want to do with an InstallationCheck
script -
and I see some examples in the list archives. My concern with this
approach
is the big floating Legacy Document warning on the InstallationCheck
page on
the Apple site.
Is there another approach, or do I just need to get over the legacy
document warning?
Thanks in advance for any opinions...
What is the big legacy warning? Is it the "this package contains a
program that determines if the software can be installed. Are you sure
want to continue?" warning?
If it's really a trouble for you, one solution could be to write a
quick Cocoa (or another language) Front-End to determine which package
should installed, add the packages in the resources and voilà!
You could even stick a Package icon on the application if you really
want it to look like a package.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden