Re: checking for OS
Re: checking for OS
- Subject: Re: checking for OS
- From: Chuck Soper <email@hidden>
- Date: Mon, 18 Apr 2005 14:59:40 -0700
At 9:37 PM +0200 4/18/05, Stéphane Sudre wrote:
On lundi, avril 18, 2005, at 08:13 AM, Chuck Soper wrote:
At 9:31 AM +0200 4/17/05, Stéphane Sudre wrote:
On samedi, avril 16, 2005, at 08:33 PM, Chuck Soper wrote:
Hello,
I'm new to this list and I apologize if the
question that I'm about to ask has already
been asked.
I have a PackageMaker installer and I need to
require a specific OS version (for example
let's say, 10.4). I would like to do this
with Requirements Checking. I have read the
documentation and looked over the examples,
but I don't see a clear example for the
simple check that I'm trying to do. Could
someone possibly post or send the actual keys
that I need to add to my Info.plist to me?
Maybe this one could work:
<key>IFRequirementDicts</key>
<array>
<dict>
<key>LabelKey</key>
<string>untitled requirement</string>
<key>Level</key>
<string>requires</string>
<key>SpecArgument</key>
<string>kern.osrelease</string>
<key>SpecType</key>
<string>sysctl</string>
<key>TestObject</key>
<string>8.0</string>
<key>TestOperator</key>
<string>>=</string>
</dict>
</array>
Thanks, I will try that. Does IFRequirementDicts live in Info.plist?
Yes.
Every time I create a new package my Info.plist is overwritten.
When you build a new package, the Info.plist file recreated indeed.
This makes it difficult to maintain
requirements. In other words, do I have
manually paste (using a a Text Editor) the
above text into the Info.plist file every time
I re-create the package?
Yes and no.
If you use the PackageMaker Front-End application, yes.
If you use the PackageMaker command-line, no.
I'm using the PackageMaker application (not the
command-line tool). I don't know how or where to
specify the IFRequirementDicts key and values
within the PackageMaker application.
I understand that after the .pkg file is created
that I can add the IFRequirementDicts key and
values to the Info.plist. I'm looking for an
automated way to do this from the PackageMaker
application.
If I can add that easily then I may want to
add an InstallationCheck script and
InstallationCheck.strings for pre-10.3 users.
I already have this partly working but the
check is done before my EULA instead of
before the installation.
Do you want to prevent the installation on
volumes which don't have at least Mac OS X
10.4 or prevent installation when the running
OS is not 10.4?
I need to only allow the installation when the
running OS is a certain version or higher.
Chuck
Ok, so you're seeing the expected behavior.
InstallationCheck is performed before the
Welcome, ReadMe or License pane.
It sounds like I shouldn't perform an
InstallationCheck because I don't like the
default behavior.
_______________________________________________
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