site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com User-agent: Thunderbird 2.0.0.22 (Macintosh/20090605) Reflatten the package, sign and we're good to go, almost. Kevin _______________________________________________ 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... We were trying to change the install progress messages to something a little more friendly. We need a signed package, so using older versions of package maker, or a non-flat format, wasn't really an option. It looks like there's no way to modify the messages through the GUI. 1) The progress messages, "Installing xxx" are just using the name of the package, xxx.pkg, in the flat package. 2) The name of the package is derived from the actual item being installed. e.g, "Foo Bar.app" becomes fooBar.pkg, and a file named com.mine.daemon.plist becomes comminedaemon.pkg. So, I used pkgutil to expand the package, renamed the actual package files in the expansion directory, and then modified Distribution to reflect the new package names. The problem is that this only works with install items which are bundles. So Foo.app I can give a new pacakge name to, or Bar.kext, but a daemon named somedaemon, which is being installed maybe in /usr/sbin, can't be renamed. If I try to rename that package I get an error from Installer when I try to install saying that there's nothing to install in that package. This is true also if the contents are a directory tree with only non-bundle items. You also can't rename things to names which have spaces. I tried doing this, using standard HTML space codes. #Foo%20Bar.pkg in Distribution expanded correctly, and there was a package named "Foo Bar.pkg", but Installer gave me the "nothing to install" error. It *did* look for the correct package name, though. Just couldn't process it. So, I got part of what I needed. I'm astonished at the lack of robustness and *extreme* lack of configurability in this stuff though. If these things are doable in a standard way, then I'm even *more* astonished at the lack of documentation. But then PackageMaker's always been a little lacking in that area compared to other dev tools... This email sent to site_archiver@lists.apple.com