Re: Problems with Metapackages in Panther.
Re: Problems with Metapackages in Panther.
- Subject: Re: Problems with Metapackages in Panther.
- From: Stéphane Sudre <email@hidden>
- Date: Mon, 22 Jan 2007 22:27:25 +0100
On lundi, janvier 22, 2007, at 10:15 AM, Dennet Menezes wrote:
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?
Hmm, I'm observing the same phenomenon. Sometimes it works, sometimes
it doesn't.
I've made some tests using InstallationCheck scripts instead of
VolumeCheck scripts and the result is better. I tried it 10 times and
every time the packages are correctly enabled and disabled.
I return 64 for error and 0 for correctness.
Of course this would require enabling the "Install on root volume only"
option.
I tried an installation and it worked fine and a later attempt show
that only the right package is enabled.
_______________________________________________
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