Re: Can I refer to files outside of a .pax archive?
Re: Can I refer to files outside of a .pax archive?
- Subject: Re: Can I refer to files outside of a .pax archive?
- From: Stéphane Sudre <email@hidden>
- Date: Mon, 3 Jul 2006 23:17:48 +0200
On lundi, juillet 3, 2006, at 09:23 PM, Nathan Herring wrote:
2. Permissions are blown up if an admin user do this
The owner of the dropped files become the admin user who dropped the
file not root as it should be.
Why is root a "should be"? Your copy will be set to have the admin
group,
which will give write permissions to all the administrators, which is
all
that is necessary. I've not tried, but I believe this happens if you
are a
regular user who tries to copy something to an admin-restricted folder
and
have to authenticate to the Finder.
Furthermore, if I chown one of my /Applications items to be me,
nathanh,
instead of root, and run repair permissions, it does not get
"corrected".
Working does not mean it's correct from a theory point of view.
It might not be an issue but next time someone runs a Repair
Permissions after installing an OS update (as if the problem was not
there before the update), he may see that the permissions were
incorrect and doesn't remember he just drag and dropped the file.
3. An alias speaks only one language
It might be nice to have an alias of the Applications folder but
Applications is not spelled "Applications" in Japanese. So one's
potential Japanese customers will wonder what Applications is supposed
to mean.
Would it be cheating to write a drop-script-style-app and gave it the
same
icon that a symlink to the Applications folder would have, and then
when you
drop it, it queries for administrative authentication? If it gets it,
it
tells the finder to copy the dropped item to the /Applications folder,
and
if not, ensures a ~/Applications folder and tells the Finder to copy it
there instead? It could be a bundle, which means it could have a
localized
file name. :) This also helps address your point #1.
This is an interesting idea but:
- you would probably experience the Security fix in Mac OS X which will
display an alert: "You are launching this application for the first
time. Do you really want to launch it?"
- it's not going to be clear in the user manual. This could give
something like this:
"To install the software, just drag and drop its icon on the
Applications folder.
Note: If your user account(1) does not have administrative
privileges(2), you will need to enter an administrative user account
name and password.
(1) a user account is the account you created when you install Mac OS X
during the setup procedure.
(2) Administrative privileges are privileges that allow you to change
some restricted settings for instance.
Note: If you do not understand the previous explanations, juts ask your
system administrator to install the whole thing using Remote desktop so
that you can go to the next chapter.
"
Point 1: Nobody ever cares. Any OS X user is an admin user, right?
No, we do care. Some of our novice users are people trying to install
it on
administratively-restricted machines (educational labs, perhaps even
some
enterprises), and won't know why things don't work.
Actually, I was sarcastic. It's amazing the number of issues that you
can discover in some applications when you run them from a standard
account.
_______________________________________________
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