site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=l3TBWtY7iSrjpEgX/rBf2kDuatjdgohO4VUHAiPTkVg=; b=cVsVHIIiHgjCP3NaOtApAyJOgzdB+sAmfrvr1vxa+CFpnqRE46eXMDJiJ3y9XGj6bT K7MSkw2vimP/LpUXEq9gPMsKgRjtHEy1Q4WA6obryOzlweACVlrk+v8vk9JW6ATieX87 MKMaOgR5TwzzSg+MEM330czkvfHEKoN8+rcpE= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=w4SJfPEAK4fmgRSmU7i9/j/Yy8NvPUvY71iETliDB+VXakTKqYGbP67sV+ldOx87LY VsFth2ahe86B8Ff+JnGsVCZXgYSo6AirTjcPoaEv9LgcLqgblHBZoaS/AzMnGTYE5q7E 59zpF7zGNxZlFZpET6C6po3eMovn4FNIzqbcw=

This indicates that you are trying to use Apple's PackageMaker. While it is the Apple tool for this, there are better ones available for free. I would suggest using Iceberg or Packages (for "old style" and "flat file" packages respectively).

Thanks, i'll take a look at that. I just wanted to make it Apple-look-like so that installation process does not differ from any other installations users had made before, even though there's a lot of addtional work is done underneath.

But regardless you can always just select the root of the filesystem as your target, and then put all of your payload in there. There are a lot of problems going down the route you have chosen, and you will get a lot of flack for doing it (Greg is one of the more vocal, so I expect him to respond as well once he makes it to work today). The first problem is that you have totally blown out any idea of system administrators being able to use the package receipt system to audit their computers. Just killed it dead. Since everything gets moved by a script there is no automate-able way of auditing this. This also means that auto-delete systems fail. This is bad. You have also opened up the potential for you to mess up in the scripting in so many ways... An example would be a system that does not properly use $3 everywhere, so now can't be used in system image creation tools like InstaDMG or System Image Utility. By going off the normal path you have made yourself responsible to know every single variation out there... is that really a burden you want to take on?

I provide my own uninstaller, but your argumentation looks reasonable. Maybe you know any good documentation available about install makers, except Apple app distribution guidlines?

Yes, there are lots. As a simple example: why are you assuming that there is only one person logged in, or that there is even one person logged in to the computer. Both cases are valid.

I guess i will have to ps -x | grep loginwindow and execute "launchctl bsexec" for every instance of loginwindow? if there's no users logged in, the loop will never be executed. Otherwise, it'll execute for every user who's logged in (well, just like in that example on that link).

We don't know exactly what you are trying to do, backing out a step or two might be a really good idea. There are a lot of people on this list that can probably better help you out if you give them the information they need to help you.

It's an NKE Kext , which is autoloaded by a "starter"-daemon and whose status is displayed by an agent in a status bar. After installing, i want these daemon and agent to be launched immediately, without reboot. _______________________________________________ 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