site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com User-agent: Thunderbird 2.0.0.14 (X11/20080505) Hi folks! So I'm trying to create a package for Leopard (not worried about backwards compatibility) that contains the following components: --- 1) A kernel extension 2) A launchd daemon 3) A launchd agent 4) An application I have organised the package into 3 sub-packages: - MyApp.kext - contains the kext only. - MyApp.framework - contains: - shared libraries - daemon - agent - launchd scripts - MyApp.app - contains: - application --- In PackageMaker, I specify 3 post-install actions: 1) Load the kext 2) Add an alias of: /Library/LaunchDaemons/myappdaemon.plist -> /Library/Frameworks/myapp.framework/Versions/Current/myappdaemon.plist 3) Add an alias of: /Library/LaunchAgents/myappdaemon.plist -> /Library/Frameworks/myapp.framework/Versions/Current/myappagent.plist --- So my problems so far are: 1) The aliases aren't created. 2) The installer insists that the user needs to log out and log in again. 3) I'd like to execute "launchctl load /path/to/launchd/scripts" afterwards, but am not quite sure how to go about it. The documentation for packagemaker is really sparse in this area. Any ideas? I'm pulling my hear out over the launchd stuff - I searched this list for launchd stuff, which returned old or unrelated issues. Would installing the launchd scripts to the /Library/Launch* paths directly be a better option? It doesn't seem as clean to me. Many many thanks for any advice. Kind regards, Tim _______________________________________________ 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... This email sent to site_archiver@lists.apple.com