• 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
PackageMaker woes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

PackageMaker woes


  • Subject: PackageMaker woes
  • From: G S <email@hidden>
  • Date: Wed, 9 Jun 2010 16:08:57 -0700

Hi all.

Is there a place to discuss PackageMaker problems?

I'm having two specifically:

1. The mpkg just isn't overwriting two of the three things it's supposed to be overwriting, and I don't get any error message.  I can't see any permission problem.  For example, I'm trying to install a component in /Library/QuickTime, and the older one never gets overwritten.  The weird thing is that the one component that does work is being written to /Library/Frameworks, so it's not a blockage on everything under /Library (and I am prompting for administrative password for the installer).

I saw a tutorial (http://s.sudre.free.fr/Stuff/PackageMaker_Howto.html) that claims you have to set up a full directory hierarchy as your source: "If you need to install a driver in the Extensions folder, you need to create a System folder, then create a Library folder within the System folder, an Extensions folder within the Library folder and finally put your driver in the Extensions folder."  I see no evidence of this in the (admittedly lame) PackageMaker documentation.  Their screen shots show the components themselves in the left pane, under their "choices".  If this hierarchy claim is true, then do I drag the topmost folder of it to the left pane to add it?  In that case, only folders are shown in that left pane.  How is it that the help-file's screen shots show the components themselves?

2. One of my components is an already-built package.  PackageMaker INSISTS on putting a path in the "Scripts directory" field on the Scripts tab for that component, pointing to [thePackage].pkg/Contents/Resources.  Then the installer build fails, complaining "Can not copy scripts".  There aren't any scripts specified!  And if I delete that path, PackageMaker will magically repopulate it with the same thing when I hit Save.  The only way I can build the installer is to delete the scripts path and kick off the build without saving.  In the resulting installer, that component does get installed.  I filed a bug against this, but how has it gone unnoticed?

Thanks for any insight on these.

Gavin
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Prev by Date: Re: Xcode 4.0 Confidential Developer Forum is now up
  • Next by Date: Re: Xcode 4.0 Confidential Developer Forum is now up
  • Previous by thread: Re: Core Data Versioning
  • Next by thread: Getting link errors weak-linking against a framework fn
  • Index(es):
    • Date
    • Thread