Using tokens in requirements
Using tokens in requirements
- Subject: Using tokens in requirements
- From: Patrick Rogers <email@hidden>
- Date: Fri, 22 Jul 2005 02:49:54 -0400
Hi. I'm new to the list and have a question about using tokens in
requirements.
I'm writing an installer for an iMovie plug-in and am trying to
implement a requirement on the iMovie version number. My requirement
needs to check the version number of the installed iMovie bundle which
can be located at either "/Applications/iMovie HD.app" or
"/Applications/iMovie.app". I already have a token defined in my
TokenDefinitions.plist that locates the iMovie application but the
requirement fails when I specify this token as the SpecArgument for my
requirement in any of the following ways:
<key>SpecType</key>
<string>bundle</string>
<key>SpecArgument</key>
<string>{iMovie}</string>
or:
<key>SpecArgument</key>
<string>iMovie</string>
or:
<key>SpecArgument</key>
<dict>
<key>/Applications/iMovie.app</key>
<string>{iMovie}</string>
</dict>
The documentation states that the SpecArgument can be a tokenized path
but does not give a syntax for a tokenized path (the syntax is only
given for path mappings). I know that my token is correctly resolved
and the requirement is correctly phrased because if I specify the
iMovie path explicitly the requirement is satisfied - it just only
matches one of the two names for the iMovie application.
Is there some secret syntax to using a tokenized path in a requirement
specification?
- Pat
_______________________________________________
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