site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Feb 3, 2009, at 9:36 PM, Brent Burton wrote: * What is the best practice for installing command line tools into /usr/local/bin? * Is there a way to Iceberg behavior out of PackageMaker w.r.t. a directory's contents? -Greg _______________________________________________ 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... Include them in the Archive.pax.gz and Archive.bom just like any other file you want to install. Sure. Bypass the GUI, don't use a pmdoc, craft your resources, and call the command-line version of packagemaker. This can be part of your automated build process. A snippet: ${INSTALL} -m 0644 -c OS_X/License.rtf ${PKGRSRCDIR} ${INSTALL} -m 0644 -c OS_X/ReadMe.rtf ${PKGRSRCDIR} ${INSTALL} -m 0644 -c OS_X/Welcome.rtf ${PKGRSRCDIR} ${INSTALL} -m 0644 -c OS_X/background.tiff ${PKGRSRCDIR} sudo chown -R root:wheel ${PKGDIR} sudo chgrp admin ${PKGDIR} /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ packagemaker \ -build -p ${PKGSRCDIR}/../${PKGNAME}.pkg \ -f ${PKGSRCDIR}/${PKGDIR} \ -r ${PKGSRCDIR}/${PKGRSRCDIR} \ -i ${PKGSRCDIR}/tmp/OS_X/Info.plist \ -d ${PKGSRCDIR}/tmp/OS_X/Description.plist * How hacky is our current tar archive payload? Any problems doing this? It's a hack. As a system administrator, I want package receipts - specifically bom files, to tell what is installed. I don't want to have to read post-xxx scripts to figure out what other stuff got installed. We'll NEVER have a working uninstall capability as long as developers use post-XXX scripts to install stuff. Your bom would mention the tar archive (which no longer exists on the target) and neglect to mention the bin tools (which now are on the target). No uninstaller could ever make sense of this. This email sent to site_archiver@lists.apple.com