Re: Installer on Mac
Re: Installer on Mac
- Subject: Re: Installer on Mac
- From: Bill Coderre <email@hidden>
- Date: Sun, 14 May 2006 15:50:08 -0700
PackageMaker can not generate Mac OS 9-style installers. They are
totally different than Mac OS X installers.
It's possible for Mac OS X Installer.app to install Classic apps, but
there are issues to make it tricky (resource forks, finding the
Blessèd System Folder, etc).
There is an SDK for the Mac OS 9 installer. I am not sure where it is
on the apple developer site. It should work fine under Mac OS 9. I
recall vaguely that it's tricky to get it running with Classic.
What precisely are you trying to accomplish?
On May 14, 2006, at 2:49 PM, Mike Fischer wrote:
Am 14.05.2006 um 21:02 schrieb "Lieven Cardoen"
<email@hidden>:
Will this work on Mac Classic? (packagemaker)
You probably could install things into the Classic folders on a Mac
OS X system using the Mac OS X Installer.app but there might be
limitations. One limitation is finding the correct folders in the
first place because they may not be there at all or they may be
moved or renamed. Also depending on user preference some things are
stored either in global folders or Mac OS X user specific folders.
(~/Library/Classic/) Apart from the user renaming the Classic
System Folder it is named differently depending on localization.
There is no generic file system name for a Classic System Folder.
In fact there might even be multiple Classic System Folders and
they need not be on the Mac OS X boot volume either.
Also, this will not work for older systems booting into Classic
(i.e. pre Mac OS X systems) because the Classic Apple Installer
will not work with Mac OS X .pkg or .mpkg Packages. It has its own
format. And I believe there is (or was) an SDK for using it.
Do you really need to support Classic in this day and age? Ask
yourself if it's worth the trouble.
My concern is that I make cd's for educational purpose, so I guess
the
cd will come into hands of customers who don't have a lot of
experience
with computers. In this case, I assume an installer is easier... The
purpose of the installer is not to go and copy files all over the
system. The application can even be run from a cd, but I wish to
force
user to run it from harddisk because there's lot of reading sound,
images, ... and running it from cd slows down the app a lot...
You could offer both drag&drop installation as well as an
Installer. That is if you have enough space on the CD. Microsoft
Office does this for example and I think it's a good idea when you
don't know what your customers prefer and your application can be
installed using d&d.
_______________________________________________
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