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: Rustam Muginov <email@hidden>
- Date: Wed, 2 Feb 2011 17:00:39 +0300
Thank you very much for your explanation, Stephane.
As far as I understand, this is not the limitation of PackageMaker but the limitation of pkg distribution?
And switching to Packages or Iceberg would not help me solve this problem?
By the way, which one of your products is preferred and more up-to-date?
--
Sincerelly,
Rustam Muginov
On Feb 2, 2011, at 4:36 PM, Stephane Sudre wrote:
> On Wed, Feb 2, 2011 at 2:29 PM, 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
>
> Maybe I should add something to explain why I'm writing this.
>
> - The possible domains are listed in the distribution script.
> - The authorization (admin password or note) is listed both in the
> distribution script and packages (and not having them in both places
> leads to strange results or errors).
>
> It would be strange if a distribution script could change the
> authorization requirements of a package (consider that a package can
> be remotely hosted and downloaded by a distribution installation).
>
> Moreover, the file permissions are defined in the package, and since
> these files can be installed in /Library, they need to be root/admin
> at least.
>
> I don't remember what the result is but I would tend to believe that
> when you change the target domain to ~/Library during installation,
> the owner and group are still root/admin after the files have been
> installed. So either that would mean that you can install root/admin
> files without being an admin or that the installation process would
> have to guess which owner and group it should set. your_uid/somegroup
> may be the obvious ones but there's no way to be sure.
>
> My $0.014
> _______________________________________________
> 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