Re: Mac OS X 10.4.7 & Relocatable packages
Re: Mac OS X 10.4.7 & Relocatable packages
- Subject: Re: Mac OS X 10.4.7 & Relocatable packages
- From: Christopher Ryan <email@hidden>
- Date: Thu, 29 Jun 2006 00:24:31 -0700
Alright, I apologize, I was focusing on the wrong issue.
This is actually expected behavior for 10.4 (to some extent). It is
unfortunate that it is causing you problems. Basically, in 10.3.9 the
relocation behavior was slightly broken such that relocation did not
work in Meta-Packages. MANY packages shipped in the world with
relocation turned on for packages within a metapackage. On 10.4 those
packages where relocating all sort of bits that shouldn't be relocated
(Kexts, Frameworks, etc), so we basically had to make the decision
that anything with a default location of /Library or /System have
relocation off by default.
This is not something we plan on fixing as there will be a number of
things it breaks in the mean time.
What you are trying to do is very common and we are looking into ways
to do this better in the future.
Chris
On jeudi, juin 29, 2006, at 08:19 AM, Christopher Ryan wrote:
I believe the problem is that the user you are running as (and
installing as because you have "None" for authentication doesn't
have permissions to write this file in /Library/Fonts.
This has nothing to do with relocation.
If it worked in 10.3.9 it means that either the file you are
installing didn't exist in 10.3.9 so your package happened to be
able to install it or that /Library/Fonts has become more locked
down since 10.3.9.
OK, I made the following tests on 10.4.7.
In all cases:
1 Package
IFPkgFlagRelocatable = true
IFPkgFlagAuthorizationAction = None
Permissions for the file is always set to 'root:admin'
Case 1:
IFPkgFlagDefaultLocation = '/'
Archive contains ./Library/Fonts/A_new_file
Result: In the "Select Destination" pane, you can select a custom
destination
Case 2:
IFPkgFlagDefaultLocation = '/'
Archive contains ./Library/Fonts/An_existing_font
Result: In the "Select Destination" pane, you can select a custom
destination
Case 3:
IFPkgFlagDefaultLocation = '/Library/Fonts/'
Archive contains ./A_new_file
Result: In the "Select Destination" pane, you CAN'T select a custom
destination
Case 4:
IFPkgFlagDefaultLocation = '/Library/Fonts/'
Archive contains ./An_existing_font
Result: In the "Select Destination" pane, you CAN'T select a custom
destination
Still doesn't look like a bug?
Problem ID #4605325
Example why this kind of situation is interesting:
I want to install a Preference Pane by default in /Library/
PreferencePanes but still let the user be able to select ~/Library/
PreferencePanes if he/she's not an admin.
_______________________________________________
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