site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com — F On Aug 7, 2008, at 4:07 PM, Fritz Anderson wrote: Earlier packages, built the same way, worked. The BOM listing for that directory is: User 0 is root; group 80 is admin. <key>IFPkgBuildVersion</key> <string>8S165</string> <!-- was 8P135 --> <key>IFPkgFlagFollowLinks</key> <false/> <!-- was true --> <key>IFPkgFlagIsRequired</key> <true/> <!-- was false --> — F _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Sorry, one more datapoint -- the tool version in my problem case is 2.1.1 . My problem persists. I am running out of ideas, and I would really appreciate some help. To summarize, my command-line-generated package skips installing a directory to /private/tmp, causing my postflight script (it checks for the directory before proceeding) to abort the installation and report it as failed. Installer.app in 10.5 reports 'Skipping "./ private/tmp/_FFExtensions"'. QUESTION: What would cause Installer.app to "skip" installing a directory? How can I prevent this? ===================== ./private 40777 0/80 ./private/tmp 40777 0/80 ./private/tmp/_FFExtensions 40777 0/80 ./private/tmp/_FFExtensions/libx-uchicago.xpi 100666 0/80 178397 657451322 ./private/tmp/_FFExtensions/nsitbookmarks.xpi 100666 0/80 7357 1514279906 ===================== I tried re-creating the package project using Iceberg. I compared the BOMs. They are identical, including the creation dates of the .xpi files. I compared the generated Info.plists. They are identical, except for textual things like package IDs, CFBundleGetInfoString, etc., EXCEPT Iceberg had these ("was" refers to my old Info.plist settings): I changed my command-line Info.plist to match these settings, but my problem persisted. A thought: The biggest change I remember is the change from the Xcode 2.4 tools to the 2.5 tools. Did the PackageMaker command-line tool change in that transition, to a form that won't work for me? And does Iceberg build packages on its own, without resort to PackageMaker? That could explain it, but if so, it sucks. Iceberg is a nice tool, but I'm maintaining several packages and a couple of plugins, and I need a makefile workflow to manage them all. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/fritza% 40uchicago.edu This email sent to fritza@uchicago.edu This email sent to site_archiver@lists.apple.com