Re: 10.4 -> 10.3 PackageMaker Problems
Re: 10.4 -> 10.3 PackageMaker Problems
- Subject: Re: 10.4 -> 10.3 PackageMaker Problems
- From: Andrew Otto <email@hidden>
- Date: Tue, 27 Mar 2007 16:52:59 -0500
On Mar 27, 2007, at 15:08 18, Stéphane Sudre wrote:
On mardi, mars 27, 2007, at 08:02 PM, Andrew Otto wrote:
In order to ask for help, I first have to describe all of the
quirky behaviors I am seeing.
I started out using PackageMaker.app distributed with OS X 10.4 to
build a simple package with a preinstall and preupgrade script.
This package .app file in my package root is not copied into the
Applications/ directory as it should be. Also, my scripts are
printing the arguments and environment variables to an install
log, and these are not set properly. For example, on 10.4, the $2
(the target installation directory) is "/Applications", and on
10.3 is is "/".
Having no luck installing a package created in 10.4 with 10.3
Installer.app, I (with much difficulty) obtained a copy of the
10.3 version of PackageMaker. This version worked almost
perfectly. My scripts ran exactly as they should ($2 is "/
Applications"), and the .app was copied into the /Applications
directory. But the app would not start up! It would bounce once
in the dock, and then die immediately. I then noticed that the
app that was installed into the /Application directory was about
2.5 MB smaller than the original! Looking inside the bundle I
found that the executable in the Contents/MacOS directory was 2.5
MB smaller than the original's executable.
So...what's going on here?! First of all, are packages created in
10.4 not compatible with 10.3's Installer.app?
It depends on whether you selected a 10.3 compatible format or not.
_Raw_ distributed scripts are not compatible with 10.3.
Given the option to not use these "Raw distributed scripts", I would
choose not to use them. I'm not really sure what you mean here. My
package is pretty simple. It consists only of a .app and pre/post
scripts that I need to run. I tried googling for info on raw
distributed scripts, but I didn't come up with much. Could you
please clarify?
Secondly, why didn't my 10.3 package install properly?
Is it a Carbon application with the resources in the resource fork
of the application? If the answer is yes, then the solution lies in
checking that you enabled the Split Forks options.
I don't believe this is a Carbon application. It was written in
Runtime Revolution, a cross platform development environment. I'm
not sure how it builds applications for Mac.
Anyway, I've *think* been able to solve the problem (although not
idealy).
By checking the "Install Fat" option in the Info tab of the 10.3
version of PackageMaker, I've been able to create a package that
installs properly on both 10.3 and 10.4.
Ideally, I wouldn't need 10.3 just to build a package. I'd like to
be able to build these packages on my own 10.4 machine.
Oh well, thanks!
-Andrew Otto
_______________________________________________
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