Hi Christian,
2011.02.09 00:44, Christian Lohmaier rašė:
On Tue, Feb 8, 2011 at 10:22 PM, Rimas Kudelis<r...@akl.lt> wrote:
2011.02.08 22:32, Christian Lohmaier rašė:
On Tue, Feb 8, 2011 at 9:15 PM, Rimas Kudelis<r...@akl.lt> wrote:
2011.02.08 18:18, Christian Lohmaier rašė:
On Tue, Feb 8, 2011 at 5:05 PM, Rimas Kudelis<r...@akl.lt> wrote:
2011.02.08 17:46, Christian Lohmaier rašė:
* You cannot install as regular user (you always have to identify as
administrator)
(authentication is done before being able to select a
target-directory)
[...]
I did, believe me.
What about the second drop-down here:
http://s.sudre.free.fr/Stuff/PM102_4.jpg ?
Look at it for a few seconds, and think about it yourself for a while.
There is *no* choice "ask for permissions when necessary".
The thing is – I don't see the other options in the drop-down.
http://developer.apple.com/tools/installerpolicy.html
Thanks.
As I understand it, the admin users would not be getting the password
prompt if this option is set to Admin Authorization. Others would be
getting it. IMO, that's a fair enough trade considering that the
installer would only allow to choose the installation disk, and not
directory (which means that /Applications/ in the main disk is the most
likely location, and it would need authorization anyway).
IMO, it's not such a big problem indeed.
But I
remember reading yesterday (or maybe the day before it) that that checkbox
is there to enable/disable the password prompt.
Yes, but then you don't get any, even when it would require a
password/administrator privileges, and then the installation will
fail.
Which is why Admin authorization is probably the best option.
copying an app from dmg is completely different from the installer
package we're discussing here.
And yes, it *does* ask for administrator privileges, when a non-admin
user tries to copy files into /Applications folder.
If you only got one user account, you probably don't notice, since
that user is administrator by default.
Yep, that's obviously my case. :)
The permissions /are/ necessary, but you don't have to deal with them
when creating the bundle (the drag'n'drop "installer"), since it's
regular copy operation and Mac OS X takes care of it and asks for
privileges when necessary.
Such a thing is not possible with the "package installer", there the
one who builds the installer has to decide *beforehand* what
privileges the installer will ask for.
If you want the user to be able to install to /Applications, you have
to require administrator privileges. But then a user who is not
administrator, and doesn't have access to an administrator account to
fulfill that requirement cannot install at all, even if the installer
would offer a target-folder selection, since the user doesn't even get
past the authorization.
How often is that the case?
So when you want to test yourself, create a non-administrator user first.
Not necessary. The installer asked me for my password even though I am
an admin. It also asked me to provide my password even when I chose to
install the package into my home directory, how lame is that!
Well, it seems like my expectations for it were a bit higher. Basically,
it looks like an incomplete product. Perhaps we could write our own
installer plugin which would check itself whether elevation is needed or
not, and then expect those who install using commandline to just use
sudo, but that's probably not really worth the trouble...
Rimas
--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***
