Good day, I am trying to migrate a build script away from using PackageMaker. The app has three components: a kernel extension, a daemon, and a normal desktop application. Including the desktop application in the package seems to be easy, however the kernel extension and the daemon require abilities that I cannot figure out how to handle. 1) Before installing the software, any previous version of the kernel extension or the daemon should be unloaded (kextunload / launchctl unload). After the install, the new kernel extension and the new daemon should be loaded (kextload / launchctl load). I have seen many references to install scripts (preupgrade and postinstall seem useful in this case), but I cannot figure out how to actually include them in the installer package. How is that done? 2) When synthesizing components, the productbuild command seems to only accept bundles as things to install. This causes a problem with the daemon - both itself and its launchd configuration file are simple files. What is the proper way to install such files? This application is not currently on the App Store, but we intend to migrate in that direction in the future. Some of the documentation I have read regarding packaging has suggested using pkgutil for generating component packages when appropriate, and using productbuild to wrap them all together. However, the man page for pkgutil says that if you intend to distribute on the App Store, you should not use pkgutil and instead use productbuild directly. However, I'm having the previously mentioned issues. What general architecture should I be going toward if I would like to be compatible with the App Store? Thanks, Andrew Keller _______________________________________________ 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: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com