Re: Problems with Metapackages in Panther.
Re: Problems with Metapackages in Panther.
- Subject: Re: Problems with Metapackages in Panther.
- From: Dennet Menezes <email@hidden>
- Date: Mon, 22 Jan 2007 14:45:35 +0530
Hi,
I tried using the exit value 33 but it still gives me inconsistent results
and I have no clue as to why. I have 11 language specific packages which I
need to club into a metapackage. The individual packages should be installed
only if there is a specific file (which points to the language) in a
particular location.
The volume check scripts are of the form
#!/bin/sh
if [ -f "/Applications/TestFolder/Dutch" ]; then
echo "Dutch-Yes"
exit 0
else
echo "Dutch-No"
exit 33
fi
with the exit value 33 as you suggested. However exit value 32 or 33 it
works perfectly fine in Tiger!
Changing the exit value to 33 got it working briefly in Panther for a
metapackage containing two packages but very inconsistently. There were
times it enabled the packages even if the VolumeCheck failed. With 11
packages I have never got it working right. Am I missing something obvious?
How can a metapackage go ahead and install a package which cannot be
installed standalone?
Thanks
Dennet.
On 1/21/07 6:36 PM, "Stéphane Sudre" <email@hidden> wrote:
>
> On jeudi, janvier 18, 2007, at 11:22 AM, Dennet Menezes wrote:
>
>> Hi,
>>
>> I have a Metapackage that contains individual packages with their own
>> VolumeCheck scripts. These packages are assigned the attribute
>> "Selected" in
>> the Metapackage Info.plist. When I install this metapackage in Tiger
>> the
>> VolumeCheck scripts for all the packages are run and they get
>> automatically
>> enabled/disabled in the Customize panel in case the script for a
>> package
>> succeeds/fails. However this is not the case in Panther where in-spite
>> of
>> the VolumeCheck scripts failing (which is verified by installing the
>> packages standalone) the metapackage goes on to allow installation for
>> all
>> the packages.
>>
>> Is there any way I can get the metapackage to validate my individual
>> packages disabling the ones whose VolumeCheck script fails in Panther
>> just
>> as it does in Tiger?
>
> From what I can see on Mac OS X 10.3.9, with the following test case:
>
> Metapackage --+-- Package 1
> |
> +-- Package 2
>
> Package 1 VolumeCheck script:
>
> #!/bin/sh
>
> exit 0
>
> Package 2 VolumeCheck script:
>
> #!/bin/sh
>
> exit 32
>
> AFAIK, according to documentation at
> http://developer.apple.com/documentation/DeveloperTools/Conceptual/
> SoftwareDistribution/Legacy_Requirements/chapter_950_section_5.html:
>
> 32 (2^5) is the first possible error value to return.
>
> If you run this metapackage, in the Customize pane, both Package 1 and
> Package 2 will be enabled and selected.
>
> If you change 32 to 33, in the Customize pane, Package 1 is enabled and
> selected. Package 2 is disabled and unselected.
>
> My $0.02
>
> P.S: this might be seen as a resent in the future as I posted a reply
> on Thursday but it hasn't appeared yet on the list.
>
-----------------------------------------------
Robosoft Technologies - Come home to Technology
_______________________________________________
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