Re: Dynamic Install Location?
Re: Dynamic Install Location?
- Subject: Re: Dynamic Install Location?
- From: Nigel Kersten <email@hidden>
- Date: Tue, 4 Sep 2007 10:24:27 -0700
On Sep 4, 2007, at 10:07 AM, Fritz Anderson wrote:
On Sep 4, 2007, at 11:12 AM, Nigel Kersten wrote:
On Sep 4, 2007, at 8:31 AM, Nigel Kersten wrote:
I was also thinking about whether I could get an mpkg preinstall
to modify the install location for one of it's containing pkgs.
Scratch that one off the list. It doesn't work unfortunately. I can
modify the Info.plist of the sub-pkg with a preflight in the mpkg,
but it doesn't get picked up, as they must all get parsed before
the preflight runs. It works happily the second time you install
the pkg, so I guess I could make an empty pkg that modified another
pkg plist and installed it as part of one of the scripts, but
that's not a particularly pleasant feeling workaround.
Even if it "worked," it wouldn't work when (not if) you distribute
your installer on read-only media.
Excellent point, and one I'd definitely forgotten, even though it's
not going to apply in this case. (pkgs are being installed via a
remote management system and aren't being distributed in a read-only
format)
So currently I'm using the method of a preflight script that:
* retrieves the ruby sitelibdir parameter
* removes /tmp/my-symlink
* symlinks sitelibdir at /tmp/my-symlink
* package destination is set to /tmp/my-symlink with follow symlinks on.
Is this really the best option for doing this? It annoys me that I
then don't get to observe the full paths with lsbom once the package
is installed.
_______________________________________________
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