• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: 10.4 -> 10.3 PackageMaker Problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 10.4 -> 10.3 PackageMaker Problems


  • Subject: Re: 10.4 -> 10.3 PackageMaker Problems
  • From: Stéphane Sudre <email@hidden>
  • Date: Tue, 27 Mar 2007 22:08:18 +0200


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.


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.


Is something wrong with the pax archive?

Not for what you want to do.

I'm kind of at a loss for what to do now. Can anyone point me in the right direction?

See above.







_______________________________________________
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


  • Follow-Ups:
    • Re: 10.4 -> 10.3 PackageMaker Problems
      • From: Andrew Otto <email@hidden>
References: 
 >10.4 -> 10.3 PackageMaker Problems (From: Andrew Otto <email@hidden>)

  • Prev by Date: 10.4 -> 10.3 PackageMaker Problems
  • Next by Date: Re: Detecting CPU Speed
  • Previous by thread: 10.4 -> 10.3 PackageMaker Problems
  • Next by thread: Re: 10.4 -> 10.3 PackageMaker Problems
  • Index(es):
    • Date
    • Thread