• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Installer packages asking for authentication in user's home directory
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Installer packages asking for authentication in user's home directory


  • Subject: Re: Installer packages asking for authentication in user's home directory
  • From: Luke Bellandi <email@hidden>
  • Date: Tue, 9 Jan 2007 14:36:54 -0800

Hi Michael,

On Jan 8, 2007, at 1:57 PM, Michael Watson wrote:

Using Package Maker 2.1.1 under Tiger, I seem to be unable to build an installer package that will allow a user to install into his or her home directory without authenticating. (That is, without pre/ post-install workarounds.)

It appears that Package Maker doesn't actually make use of, say, something like NSFileManager to determine whether or not a user has write access to an area, and then prompt if necessary for authentication. It's using its own internal rule set, which just doesn't seem to be very smart:

1. I have to choose a default installation directory.
2. If I choose "Administrator" or "root" for the authentication option, the user is prompted to authenticate even for places he or she has write access. Unacceptable.
3. If I choose "none" for the authentication option, the user is not prompted for authentication under any circumstance, and thus cannot choose to install to those places that would normally trigger an authentication prompt.


Is there a way to solve this, aside from pre/post-install workarounds?

No. The installer either installs all files as the user (when authentication is none), or applies the ownership of all of the files from when they were packaged (when authentication is admin or root). There's no support for a hybrid case, except by using scripts as you say.


Generally it makes more sense to try to stick to one domain. What are you installing that requires pieces to be installed in both the user *and* the system domain?

- Luke



--
Michael Watson

_______________________________________________
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

_______________________________________________ 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
  • Follow-Ups:
    • Re: Installer packages asking for authentication in user's home directory
      • From: Michael Watson <email@hidden>
References: 
 >Installer packages asking for authentication in user's home directory (From: Michael Watson <email@hidden>)

  • Prev by Date: Installer packages asking for authentication in user's home directory
  • Next by Date: Re: Installer packages asking for authentication in user's home directory
  • Previous by thread: Installer packages asking for authentication in user's home directory
  • Next by thread: Re: Installer packages asking for authentication in user's home directory
  • Index(es):
    • Date
    • Thread