January 2010 - Installer-dev

Packagemaker command line tool not preserving resource forks?
by Colin Cornaby 05 Jan '10

05 Jan '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com I'm working on a project where the files contain resource forks. The installer is being built using the packagemaker command line tool on 10.6. When the files are installed, attributes such as the file type and custom icons are being lost. Is there a way to preserve them? I know it would be better to move to file extensions, but at this point I just need to get a new installer out. Thanks, Colin _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

RE: Preinstall/Postinstall actions not created using CLI packagemaker
by Ben Staveley-Taylor 05 Jan '10

05 Jan '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Organization: Oracle Thread-index: AcqNp5kIeFpkwcRQQ+K7+2ovqdULrAAPVYYg Hi Paul It's been a while since I struggled with this and things might have improved since then, but I never got CLI packagemaker to work well for me. I suffered a litany of problems where the output package was simply wrong, localisations were ignored, or the .pmdoc settings (e.g. the "allow relocation" setting) would mysteriously get reset to their defaults. I'm sure there's a trick to fixing these problems, but I could never trust the output of my builds. In the end I switched to using Iceberg for my installer building, and it was much more reliable. Like packagemaker, it is possible to run it from the command line in an automated build. I'd recommend it if you haven't already come across it. -- Ben. -----Original Message----- From: Paul Forgey [mailto:paulf@tessier-ashpool.net] Sent: Tue 05 January 2010 01:37 To: Ben Staveley-Taylor Cc: installer-dev(a)lists.apple.com Subject: Re: Preinstall/Postinstall actions not created using CLI packagemaker Actions do not seem to work with command line built packages in this version of packagemaker (and still happening in XCode 3.2.1). I, too, would like to know if anybody has found a workaround for this. On Sep 9, 2009, at 5:04 AM, Ben Staveley-Taylor wrote: > I am running packagemaker from XCode 3.1.2. > > I have created a .pmdoc for my installer, and defined some preinstall and postinstall actions in the Actions tab of the overall Distribution package (not an individual package). > > When I build the installer from the GUI, it all works. When I build it from the command line as I would do in a build script, the preinstall and postinstall actions do not run. The difference is that when built from the CLI, the pseudo-packages that contain the actions just aren't being created. > > Interactively built from PackageMaker GUI, I get this package structure: > > MyInstaller.mpkg > Contents > Packages > MyPackage.pkg > MyPackagePostflight.pkg > MyPackagePreflight.pkg > > Built from packagemaker CLI tool, I get this package structure: > > MyInstaller.mpkg > Contents > Packages > MyPackage.pkg > > My packagemaker command line is: > > packagemaker --doc "<path to MyInstaller.pmdoc>" \ > --out "<path to MyInstaller.mpkg>" \ > --id com.mycompany.myproduct.pkg \ > --verbose > > Has anybody else come across this? What's the vital command line parameter I am missing? > > Thanks > > Ben Staveley-Taylor > Oracle > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Preinstall/Postinstall actions not created using CLI packagemaker
by Paul Forgey 05 Jan '10

05 Jan '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Actions do not seem to work with command line built packages in this version of packagemaker (and still happening in XCode 3.2.1). I, too, would like to know if anybody has found a workaround for this. On Sep 9, 2009, at 5:04 AM, Ben Staveley-Taylor wrote: > I am running packagemaker from XCode 3.1.2. > > I have created a .pmdoc for my installer, and defined some preinstall and postinstall actions in the Actions tab of the overall Distribution package (not an individual package). > > When I build the installer from the GUI, it all works. When I build it from the command line as I would do in a build script, the preinstall and postinstall actions do not run. The difference is that when built from the CLI, the pseudo-packages that contain the actions just aren't being created. > > Interactively built from PackageMaker GUI, I get this package structure: > > MyInstaller.mpkg > Contents > Packages > MyPackage.pkg > MyPackagePostflight.pkg > MyPackagePreflight.pkg > > Built from packagemaker CLI tool, I get this package structure: > > MyInstaller.mpkg > Contents > Packages > MyPackage.pkg > > My packagemaker command line is: > > packagemaker --doc "<path to MyInstaller.pmdoc>" \ > --out "<path to MyInstaller.mpkg>" \ > --id com.mycompany.myproduct.pkg \ > --verbose > > Has anybody else come across this? What's the vital command line parameter I am missing? > > Thanks > > Ben Staveley-Taylor > Oracle > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

[Flat Package Editor] How to make it take changes into account
by Iceberg-Dev 04 Jan '10

04 Jan '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version :content-transfer-encoding:message-id:content-type:to:from:subject :date:x-mailer; bh=g+s+WMZ92TgRVzTEaZEF0ZfcEzuTRljHri6s9yb8Wo0=; b=Gn20ZQI4EF8iXPpR3woeP4iS3Ot284ROME/0XYWYY7iNU5jzSaJsumuzskQ9G+YWm/ CCz471Mzs4kThrdrKeHoQlYAaTvAmjpZr2j4tHI5vUmPZhPboUHDrbPfIbA4n7f0Psvm nm4SW+Cfr0k6yV+/8g4Q1bGAQFxrtJkwo0upk= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:content-transfer-encoding:message-id:content-type:to :from:subject:date:x-mailer; b=asd6gghXeEU4rH54U7D7AldtR++BpJ81KvxG3dmyrrH28R4vZmppZzfMqDBIWyJqoO YdbWx+8HFPeFDK2Oa8T8aMkNQ6mVV0ukOZ3tjgwBPQh/cDuJjJELEnDt711eFN2tsTSe ZaamZJfZWLs/xoqzmy7JnI0G4vmis4v7jTcOA= (*) Flat Package Editor is the utility embedded in PackageMaker. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… If you make a change in Flat Package Editor (*), like deleting the Scripts item or deleting the PackageInfo file to replace it with a better one, you may have found that if you save the modified document and opened it again, your changes would not be taken into account. This is due to a bug in Flat Package Editor (Bug ID# 7508018). Basically, files are not closed when they should be. So whenever you need to use Flat Package Editor to make changes in a Flat package, _QUIT_ the application after saving your changes. This way, you will be able to see your changes. This email sent to site_archiver(a)lists.apple.com

1 0

Re: packagemaker not working
by Greg Neagle 04 Jan '10

04 Jan '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com -Greg On Dec 30, 2009, at 3:46 PM, Bill Appleton wrote: hi all, if you use the new command line interface (it is easy to switch from the backwards compatibility interface) there is the option -w this turns off auto relocation and it works best, bill On Dec 30, 2009, at 11:04 AM, Bill Appleton wrote: defaults write FOO.pkg/Contents/Info IFPkgFlagRelocatable -bool NO As for "flat" packages, you could do this: pkgutil --expand FOO.pkg FOO.pkgsrc perl -i -pe 's/relocatable\s*=\s*"true"/relocatable="false"/' FOO.pkgsrc/PackageInfo pkgutil --force --flatten FOO.pkgsrc FOO.pkg These hacks "slam" the relocatable flag to false. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Thanks, Bill -- this seems to be a relatively new addition to packagemaker (new with the SL release). Bill C's approach works with the Leopard tools, so it's still helpful to know about. On Wed, Dec 30, 2009 at 3:01 PM, Bill Coderre <bc(a)apple.com> wrote: is there a definitive way to stop the relocation in the latest version of packagemaker used from the command line? I wrote an email a while ago explaining how to remove the relocation info from a package after it's built: Here is a shell script for "bundle" format installer packages which might help: They're "hacks" because they "know" the format of the bundle and flat packages. Package Formats are not officially documented. On the other hand, Installer.app in 10.5.5 still installs packages from 10.1 era (late 2001), so it'll probably be a while before the hacks stop working. Anyway, this might be enough to get your problem solved sufficiently that you can get back to writing software. This email sent to site_archiver(a)lists.apple.com

1 0