Re: Installer with per-machine and per-user selection
Re: Installer with per-machine and per-user selection
- Subject: Re: Installer with per-machine and per-user selection
- From: Stephane Sudre <email@hidden>
- Date: Wed, 2 Feb 2011 19:16:12 +0100
On Wed, Feb 2, 2011 at 5:28 PM, Don Montalvo <email@hidden> wrote:
>> Stephane Sudre <email@hidden> wrote:
>>
>> On Wed, Feb 2, 2011 at 12:27 PM, Rustam Muginov <email@hidden> wrote:
>>
>>> Hello all.
>>> I am trying to create an installer, using PackageMaker, which would allow some items to be installed either into /Library or into ~/Library folder.
>>> I can build such installer, it does allow me to select between "all users" and "only current user", but it does require administrator password for both installations.
>>> If i remove "admin authorization", when the installation to the /Library would fail.
>>> Is it possible to get rid from the redundant password request while installing to "~/Library" but ask for password while installing to "/Library"?
>>
>> No, it's not possible
>
> Isn't it possible for the pkg to install into /tmp/librarystuff and then use a postflight loop script to copy into existing ~/Library as well as the User Template (for future users)?
>
> That's how we deploy stuff that goes to all users on the Mac.
This is a possible workaround. But it has the following issues:
- it hides the files that have been really installed to the
installation data base.
- it would not solve the admin password issue AFAIK. (having 2
packages in the same distribution: one for / and one for ~/ would not
solve it either)
- and, IIRC, sometimes, it can cause troubles with the receipt on some
OS (I was playing with a bundle package when I experienced this).
_______________________________________________
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