Re: creating alias during installation
Re: creating alias during installation
- Subject: Re: creating alias during installation
- From: John Daniel <email@hidden>
- Date: Tue, 13 Feb 2007 20:58:36 -0600
On Feb 13, 2007, at 12:01 PM, Luke Bellandi wrote:
Actually, it depends. Apple's recommendations for package
distribution are not that cut and dry. The sort of distribution
mechanism you should be using depends on three things:
[1] the complexity of the install you're performing
[2] your desire to present the user with addition information or
plugins during the installation
[3] the computer-savvy level you expect of your customers
So for non-complex projects (e.g., a self-contained application),
where you don't need or want to display a read-me, license
agreement (yes, that functionality is available in disk images as
well), summary panel, or use installer plugins, and where you
expect users will have a good understanding of how to use the file
system, then a drag and drop installer is an appropriate avenue to
consider.
For other situations, you may need/prefer to use an installer
package, if only to hold users' hands through the installation
process. Installation is an intimidating process for a lot of
novice users. Using the Installer as opposed to asking them to
drag and drop an icon can be somewhat reassuring.
That is why I went to an Installer.
But I still don't fully understand the PackageMaker installer. My
first installer worked great. But, I was using it incorrectly by
installing into /Applications with No Authorization. It seems like
the only correct option is to authenticate as administrator and
install applications as root. My application doesn't need that and a
halfway savvy user would know that and wonder why it is asking for
administrator rights - as well they should.
It would be nice to have a drag-n-drop-type installer that doesn't
need administrator rights but can install into /Applications. I have
an installer for Privoxy that definitely needs PackageMaker. It
should authenticate and run/install as root. My dilemma is a simple
installer for those intimidated novice users. If they don't have
rights to install in /Applications, it will tell them. If they do
have rights, it should install as easy as dragging-n-dropping. The
files it creates should be owned by the user installing, whomever
they might be and whatever their uid might be.
Perhaps when I get time I might try to create that with my
"incorrect" no authenticate installer and better scripts.
John
_______________________________________________
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