• 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
Apparent PackageMaker tool bug (was "No package identifier specified")
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Apparent PackageMaker tool bug (was "No package identifier specified")


  • Subject: Apparent PackageMaker tool bug (was "No package identifier specified")
  • From: Fritz Anderson <email@hidden>
  • Date: Thu, 28 Jun 2007 15:51:31 -0500

Suggestions, on-list and off-, that I may not have set the package identifier, were inapposite to my problem (which I'd oversimplified in the hope of getting replies on this go-round).

More examination shows my problem to be a strange interaction between the PackageMaker tool and recursive calls to a GNU makefile.

When doing a recursive make (make -C subdir all), GNUmake changes the working directory to subdir, but leaves the bash environment variable PWD unchanged. (Googling leads me to believe that POSIX is okay with this behavior.) Every shell command I've seen performs correctly when this happens. Except PackageMaker.

It appears that PackageMaker does not rely on file-name parameters being relative to the current working directory. Instead, it makes these file names relative to PWD.

So in a recursive make, "PackageMaker ... -i Info.plist" tries to pull Info.plist from PWD, the _parent_ directory.

The workaround seems to be to set PWD before invoking PackageMaker:

PWD=`pwd` \
PackageMaker -build -p build/CPBase.pkg -f ./root -b /tmp -ds \
   -r resources -i Info.plist -d Description.plist

This can't be an uncommon situation — surely others are building mpkgs by having makefiles build the constituent pkgs first and the mpkg from them?

Is this, as I believe, a bug in PackageMaker? I want to do a reality check before slogging through a Radar report.

	— F

On 28 Jun 2007, at 1:11 PM, Fritz Anderson wrote:

I sent this question about a week ago, but perhaps the abundant detail I included scared people off.

Short question (which may lead to more):

What does it mean when the PackageMaker tool emits the error message:

The package could not be created because of the following errors:
No package identifier specified.

_______________________________________________ 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
References: 
 >PackageMaker tool: "No package identifier specified" (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: PackageMaker tool: "No package identifier specified"
  • Next by Date: Meta-package checking for Intel vs PPC
  • Previous by thread: Re: PackageMaker tool: "No package identifier specified"
  • Next by thread: Meta-package checking for Intel vs PPC
  • Index(es):
    • Date
    • Thread