Re: Distribution Project Catch-22
Re: Distribution Project Catch-22
- Subject: Re: Distribution Project Catch-22
- From: Christopher Ryan <email@hidden>
- Date: Fri, 31 Mar 2006 13:50:02 -0800
Distribution Project, as created by Package Maker creates a meta
package (.mpkg) with a Distribution (.dist) inside.
On 10.4 the entire user experience and decisions are made from the
distribution script alone, and the .mpkg acts purely as a bundle to
hold distribution script resources (ReadMe, License, Localizations).
On 10.3, the Meta Package acts like any old meta package, VolumeCheck
scripts should run as normal and allow you to block the package from
installing on previous systems (in fact, the VolumeCheck in the
metapackage can always fail, since on newer systems, the Distribution
script takes precedence. InstallationCheck's do not work from
MetaPackages in 10.3 and earlier.
Please let me know if you need an example.
Chris
Hi,
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?
Wayne
_______________________________________________
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
_______________________________________________
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