Re: how a single product will install to different locations
Re: how a single product will install to different locations
- Subject: Re: how a single product will install to different locations
- From: Bill Coderre <email@hidden>
- Date: Tue, 1 Jul 2008 14:50:06 -0700
On Jul 1, 2008, at 2:18 PM, Paul Miller wrote:
I'm a plugin developer too, and unfortunately, the sad reality is
that plugin installation for Adobe Photoshop (and other hosts) is
our #1 customer support issue. Customers generally have several
versions of Photoshop or After Effects or whatever installed, and
the plugin locations of these products is usually something like
/Applications/Adobe Photoshop CS3/Plug-ins/
A "simple" Mac installer just doesn't know enough to help the user
install their plugin into that path, since we can't easily find out
which Adobe products (or versions) they may have installed.
I agree that these needs are not well served by Installer.app.
The solution I gave, I think it's a commonly-used approach. I added a
few security tweaks. It can work just fine in 10.3, probably 10.1.
Unfortunately, without a completely insane amount of work or writing
custom installer plugins or even a custom installer (as Adobe did),
we're literally *forced* to ask the user something they may not
necessarily know, or forget to change with the "Choose Location"
button.
This is probably why I see this question asked almost once a week. I
asked it myself a few months back.
On Windows, this is a relatively trivial thing with most installer
tools. Or, we can easily search out the latest version of Photoshop
(that we know about) and default the install location to that. I
still can't even do something as simple as that with installer
scripts (at least in pre-Leopard, but you know, we still have to
support Tiger users too!).
It's clear that Installer.app's "find" functionality is insufficient
for this. Installer.app is also not capable of installing one "thing"
in several places.
While we're on the subject, why don't you guys release Installer
upgrades to previous OS versions, so we can continue to use your
latest installer stuff and still support all supported platforms?
Every time there is a new OS X release, there's some new installer
change, and oh, none of them are backward compatible. Makes me want
to just write my own installer, and I'm probably not the only one. :-(
There's a lot of reasons, but I think Apple should supply an Official
Answer to this, and I'm not the one to do that.
_______________________________________________
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