Re: FSCopyObjectAsync: useless and crippled
Re: FSCopyObjectAsync: useless and crippled
- Subject: Re: FSCopyObjectAsync: useless and crippled
- From: Scott Ellsworth <email@hidden>
- Date: Mon, 16 May 2005 11:48:41 -0700
On May 15, 2005, at 7:39 PM, Andreas Mayer wrote:
Am 16. Mai 2005 um 02:59 Uhr schrieb Mark Munz (DevList):
Well OK a user probably wouldn't copy a file into Library, but an
application that needs to install files in /Library/ definitely
would.
Why would any application *need* to install anything in /Library?
If it's only installed for the current user, ~/Library will do just
fine.
If the app is to be placed in /Applications - well, then you'll
need an installer anyway ...
Let me just chime in on the "drag install and first run fix" side as
well. From a user point of view, it does not get much easier than
dragging the app to applications, then authenticating with the admin
username. From an IT point of view, if you let the admin username
and password get into user hands, you have problems, so it seems to
be a reasonable balance.
The corrolaly to that is simple - I hate apps that require
authentication on the first run, unless they are really doing
something that requires it. Installing a bbedit command line tool
makes sense, as it is an optional part of the run. Installing a font
in /Library/Fonts, when it could go in ~Library/Fonts bugs me.
Take it for what you paid for it.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden