Re: PackageMaker and custom folder icons
Re: PackageMaker and custom folder icons
- Subject: Re: PackageMaker and custom folder icons
- From: Stéphane Sudre <email@hidden>
- Date: Tue, 12 Feb 2002 19:30:45 +0100
On Tuesday, February 12, 2002, at 07:18 PM, Erik M. Buck wrote:
Use a disk image. The first time a user starts the application, copy
or
move the relevant items to /Library/Frameworks, /Library/StartupItems,
/Library/Preferences and /usr/bin. The user will need admin
privileges
to
do that anyway, and your application can take care of authenticating
the
user and or insisting that the user is an administrator. Finally,
don't
copy
things to /Library/StartupItems or /usr/bin without a really good
reason,
and ask the user for confirmation before doing it.
You're kidding?
No. You seem to be agreeing below. The user must be admin and or
authenticate to copy items into /Library/StartupItems or
/Library/Frameworks. We seem to be in complete agreement.
You should be doing politics :-)
Another utility of Disk Images is simple drag and drop instalation.
Yes but for simple applications. As soon as an application is made of 2
components, an installer is needed.
The various installer applications are all broken on OS X in one way or
another.
Or not completely documented.
And last killer point: egg and chicken problem.
A StartupItem is launched at Startup. If the StartupItem is not
launched, the Application doesn't launch. So It's not possible to copy
the StartupItem. And so on.
There is no chicken and egg problem because the user has to install the
application at some time. When the user copies the application from a
disk
image and double clicks it the first time, the user is authenticated
and the
copying takes place. From then on, the application (or another) is
started
automatically.
That leads to creating an installer code, doesn't it? And if there's a
StartupItem involved, then the application is not started but the Mac
is rebooted.
If you're installing an application on a machine using this, every user
will have to install it and overwrite the Application in /Applications.
There is no reason to overwrite an application in /Applications. If
multiple users are sharing an application and or frameworks, there is no
need to copy or install anything when another user wants to use the
applications. There is also /Network/Applications and
/Network/Library/Frameworks which is probably where third party
applications
that are shared by multiple users should be installed. The whole point
is
that /Library and /Applications are reasonably reserved for components
that
come with the operating system. It is not a good idea to clutter them
with
user applications.
~/Library and /Library "are" for 3rd party components. /System/Library
is for components that came with the OS.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.