December 2008 - Installer-dev

Re: PackageMaker automation
by Everette Clemmer 10 Dec '08

10 Dec '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acla8+tr7HNwgbBXPkux47QmNFFk6g== Thread-topic: PackageMaker automation User-agent: Microsoft-Entourage/12.14.0.081024 Yeah, that's where my output is coming from...."packagemaker" is aliased to /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ PackageMaker on my system. I'm really confused about this....it seems like CI installer integration would be a fairly basic need for anyone building a mac app with a regular release cycle. Everette On 12/10/08 12:40 PM, "Dan Spirlock" <dans(a)bias-inc.com> wrote: > I've gotten that crash before as well. One thing I've had success with > is rather than calling the PackageMaker command line utility, which is > just an alias to the PackageMaker binary in the app bundle, invoke the > PackageMaker executable binary directly: > > /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ > PackageMaker --doc some.pmdoc > > Hope that helps > > - Dan > > > > On Dec 10, 2008, at 8:35 AM, Everette Clemmer wrote: > >> Yeah it looks like using the --doc flag with a .pmdoc file is still >> broken. >> If I understand the man page correctly, the following should output a >> package file in the same directory as the input .pmdoc file: >> >> packagemaker --doc some.pmdoc >> >> Instead I get the following stack trace which seems to indicate that >> there's >> a problem in the command line packagemaker's interpretation of one >> of the >> arguments in the .pmdoc xml. The same .pmdoc file works like a charm >> when >> run from the GUI. >> >> $ packagemaker --doc 3.3.5Patch.pmdoc >> 2008-12-10 11:29:12.940 PackageMaker[77957:10b] Setting to : 0 (null) >> 2008-12-10 11:29:12.943 PackageMaker[77957:10b] Setting to : 0 >> com.foo.bar >> 2008-12-10 11:29:12.945 PackageMaker[77957:10b] relocate: (null) 0 >> 2008-12-10 11:29:12.946 PackageMaker[77957:10b] *** Terminating app >> due to >> uncaught exception 'NSInvalidArgumentException', reason: '*** >> -[NSXMLDocument initWithXMLString:options:error:]: nil argument' >> 2008-12-10 11:29:12.946 PackageMaker[77957:10b] Stack: ( >> 2533658955, >> 2518863419, >> 2533658411, >> 2533658474, >> 2448842100, >> 453375, >> 447724, >> 436213, >> 435514, >> 9990, >> 9922 >> ) >> Trace/BPT trap >> >> >> >> On 12/1/08 5:16 PM, "Rick Cochran" <rcc2(a)cornell.edu> wrote: >> >>> Iceberg-Dev wrote: >>>> >>>> On Dec 1, 2008, at 4:00 PM, Everette Clemmer wrote: >>>> >>>>> Hi all, >>>>> >>>>> I¹m trying to set up a CI environment where one step involves >>>>> building >>>>> an installation package via package maker. I¹m fairly familiar with >>>>> creating packages in the PM GUI and can create basic packages via >>>>> the >>>>> command line. I¹m curious about what seems to be a vast disconnect >>>>> between the options available in the GUI compared to those >>>>> available >>>>> on the command line; the latter of which appears to be very feature >>>>> poor from the man page description. I¹ve done quite a bit of >>>>> searching >>>>> in the ADC docs and on Google only to come up very frustrated. >>>>> Documentation is scarce at best and what is out there tends to be >>>>> in >>>>> excess of three years old. Does anyone on this list know of any >>>>> current, up to date, documentation on the command line >>>>> functionality >>>>> of packagemaker? I¹m specifically interested in setting >>>>> installation >>>>> requirements. I¹d also love to see some example scripts using it if >>>>> anyone has them lying around. >>>> >>>> AFAIK, the command line version of PackageMaker accepts PackageMaker >>>> project as input. So it's as rich as the UI version. >>> >>> My experience is that this doesn't work. As I remember, PackageMaker >>> crashed. >>> -Rick >>> _______________________________________________ >>> 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/eclemmer%40rosettastone >>> .c >>> om >>> >>> This email sent to eclemmer(a)rosettastone.com >> >> _______________________________________________ >> 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/dans%40bias-inc.com >> >> This email sent to dans(a)bias-inc.com > > > > > _______________________________________________ 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: PackageMaker automation
by Russ 10 Dec '08

10 Dec '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=wL5x41Qh4eq30yjeztkk+FW9dTMnznRk5mq3oMF6QfY9RmMuOUa/l2uMsSCnKTE6HGRUoT8lKH7/H+fJ7HcNnbGE5MSBVcq0uIJHHzE5XYU5Y7QejZQ0L+zAqaYQBNBahfn6kLznwiGyGK38wN26tB+c/B80RpmGR3PiF9/4GD0=; I haven't had trouble running packagemaker from my build script either; I do run the executable directly as Dan mentioned. I use --out ... to put the result somewhere as well. Russ ----- Original Message ---- From: Dan Spirlock <dans(a)bias-inc.com> To: Everette Clemmer <eclemmer(a)rosettastone.com> Cc: installer-dev(a)lists.apple.com Sent: Wednesday, December 10, 2008 12:40:33 PM Subject: Re: PackageMaker automation I've gotten that crash before as well. One thing I've had success with is rather than calling the PackageMaker command line utility, which is just an alias to the PackageMaker binary in the app bundle, invoke the PackageMaker executable binary directly: /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker --doc some.pmdoc Hope that helps - Dan On Dec 10, 2008, at 8:35 AM, Everette Clemmer wrote: > Yeah it looks like using the --doc flag with a .pmdoc file is still broken. > If I understand the man page correctly, the following should output a > package file in the same directory as the input .pmdoc file: > > packagemaker --doc some.pmdoc > > Instead I get the following stack trace which seems to indicate that there's > a problem in the command line packagemaker's interpretation of one of the > arguments in the .pmdoc xml. The same .pmdoc file works like a charm when > run from the GUI. > > $ packagemaker --doc 3.3.5Patch.pmdoc > 2008-12-10 11:29:12.940 PackageMaker[77957:10b] Setting to : 0 (null) > 2008-12-10 11:29:12.943 PackageMaker[77957:10b] Setting to : 0 com.foo.bar > 2008-12-10 11:29:12.945 PackageMaker[77957:10b] relocate: (null) 0 > 2008-12-10 11:29:12.946 PackageMaker[77957:10b] *** Terminating app due to > uncaught exception 'NSInvalidArgumentException', reason: '*** > -[NSXMLDocument initWithXMLString:options:error:]: nil argument' > 2008-12-10 11:29:12.946 PackageMaker[77957:10b] Stack: ( > 2533658955, > 2518863419, > 2533658411, > 2533658474, > 2448842100, > 453375, > 447724, > 436213, > 435514, > 9990, > 9922 > ) > Trace/BPT trap > > > > On 12/1/08 5:16 PM, "Rick Cochran" <rcc2(a)cornell.edu> wrote: > >> Iceberg-Dev wrote: >>> >>> On Dec 1, 2008, at 4:00 PM, Everette Clemmer wrote: >>> >>>> Hi all, >>>> >>>> I’m trying to set up a CI environment where one step involves building >>>> an installation package via package maker. I’m fairly familiar with >>>> creating packages in the PM GUI and can create basic packages via the >>>> command line. I’m curious about what seems to be a vast disconnect >>>> between the options available in the GUI compared to those available >>>> on the command line; the latter of which appears to be very feature >>>> poor from the man page description. I’ve done quite a bit of searching >>>> in the ADC docs and on Google only to come up very frustrated. >>>> Documentation is scarce at best and what is out there tends to be in >>>> excess of three years old. Does anyone on this list know of any >>>> current, up to date, documentation on the command line functionality >>>> of packagemaker? I’m specifically interested in setting installation >>>> requirements. I’d also love to see some example scripts using it if >>>> anyone has them lying around. >>> >>> AFAIK, the command line version of PackageMaker accepts PackageMaker >>> project as input. So it's as rich as the UI version. >> >> My experience is that this doesn't work. As I remember, PackageMaker >> crashed. >> -Rick >> _______________________________________________ >> 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/eclemmer%40rosettaston… >> om >> >> This email sent to eclemmer(a)rosettastone.com > > _______________________________________________ > 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/dans%40bias-inc.com > > This email sent to dans(a)bias-inc.com _______________________________________________ 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/matchmovie%40yahoo.com This email sent to matchmovie(a)yahoo.com _______________________________________________ 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: PackageMaker automation
by Dan Spirlock 10 Dec '08

10 Dec '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hope that helps - Dan On Dec 10, 2008, at 8:35 AM, Everette Clemmer wrote: packagemaker --doc some.pmdoc On 12/1/08 5:16 PM, "Rick Cochran" <rcc2(a)cornell.edu> wrote: On Dec 1, 2008, at 4:00 PM, Everette Clemmer wrote: Hi all, AFAIK, the command line version of PackageMaker accepts PackageMaker project as input. So it's as rich as the UI version. My experience is that this doesn't work. As I remember, PackageMaker crashed. -Rick _______________________________________________ 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/eclemmer%40rosettaston… om _______________________________________________ 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/dans%40bias-inc.com _______________________________________________ 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.… I've gotten that crash before as well. One thing I've had success with is rather than calling the PackageMaker command line utility, which is just an alias to the PackageMaker binary in the app bundle, invoke the PackageMaker executable binary directly: /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ PackageMaker --doc some.pmdoc Yeah it looks like using the --doc flag with a .pmdoc file is still broken. If I understand the man page correctly, the following should output a package file in the same directory as the input .pmdoc file: Instead I get the following stack trace which seems to indicate that there's a problem in the command line packagemaker's interpretation of one of the arguments in the .pmdoc xml. The same .pmdoc file works like a charm when run from the GUI. $ packagemaker --doc 3.3.5Patch.pmdoc 2008-12-10 11:29:12.940 PackageMaker[77957:10b] Setting to : 0 (null) 2008-12-10 11:29:12.943 PackageMaker[77957:10b] Setting to : 0 com.foo.bar 2008-12-10 11:29:12.945 PackageMaker[77957:10b] relocate: (null) 0 2008-12-10 11:29:12.946 PackageMaker[77957:10b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSXMLDocument initWithXMLString:options:error:]: nil argument' 2008-12-10 11:29:12.946 PackageMaker[77957:10b] Stack: ( 2533658955, 2518863419, 2533658411, 2533658474, 2448842100, 453375, 447724, 436213, 435514, 9990, 9922 ) Trace/BPT trap Iceberg-Dev wrote: I’m trying to set up a CI environment where one step involves building an installation package via package maker. I’m fairly familiar with creating packages in the PM GUI and can create basic packages via the command line. I’m curious about what seems to be a vast disconnect between the options available in the GUI compared to those available on the command line; the latter of which appears to be very feature poor from the man page description. I’ve done quite a bit of searching in the ADC docs and on Google only to come up very frustrated. Documentation is scarce at best and what is out there tends to be in excess of three years old. Does anyone on this list know of any current, up to date, documentation on the command line functionality of packagemaker? I’m specifically interested in setting installation requirements. I’d also love to see some example scripts using it if anyone has them lying around. This email sent to eclemmer(a)rosettastone.com This email sent to dans(a)bias-inc.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker automation
by Everette Clemmer 10 Dec '08

10 Dec '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acla5Uum9kCnJMT87Ueo4iIaOXL99w== Thread-topic: PackageMaker automation User-agent: Microsoft-Entourage/12.14.0.081024 Yeah it looks like using the --doc flag with a .pmdoc file is still broken. If I understand the man page correctly, the following should output a package file in the same directory as the input .pmdoc file: packagemaker --doc some.pmdoc Instead I get the following stack trace which seems to indicate that there's a problem in the command line packagemaker's interpretation of one of the arguments in the .pmdoc xml. The same .pmdoc file works like a charm when run from the GUI. $ packagemaker --doc 3.3.5Patch.pmdoc 2008-12-10 11:29:12.940 PackageMaker[77957:10b] Setting to : 0 (null) 2008-12-10 11:29:12.943 PackageMaker[77957:10b] Setting to : 0 com.foo.bar 2008-12-10 11:29:12.945 PackageMaker[77957:10b] relocate: (null) 0 2008-12-10 11:29:12.946 PackageMaker[77957:10b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSXMLDocument initWithXMLString:options:error:]: nil argument' 2008-12-10 11:29:12.946 PackageMaker[77957:10b] Stack: ( 2533658955, 2518863419, 2533658411, 2533658474, 2448842100, 453375, 447724, 436213, 435514, 9990, 9922 ) Trace/BPT trap On 12/1/08 5:16 PM, "Rick Cochran" <rcc2(a)cornell.edu> wrote: > Iceberg-Dev wrote: >> >> On Dec 1, 2008, at 4:00 PM, Everette Clemmer wrote: >> >>> Hi all, >>> >>> I¹m trying to set up a CI environment where one step involves building >>> an installation package via package maker. I¹m fairly familiar with >>> creating packages in the PM GUI and can create basic packages via the >>> command line. I¹m curious about what seems to be a vast disconnect >>> between the options available in the GUI compared to those available >>> on the command line; the latter of which appears to be very feature >>> poor from the man page description. I¹ve done quite a bit of searching >>> in the ADC docs and on Google only to come up very frustrated. >>> Documentation is scarce at best and what is out there tends to be in >>> excess of three years old. Does anyone on this list know of any >>> current, up to date, documentation on the command line functionality >>> of packagemaker? I¹m specifically interested in setting installation >>> requirements. I¹d also love to see some example scripts using it if >>> anyone has them lying around. >> >> AFAIK, the command line version of PackageMaker accepts PackageMaker >> project as input. So it's as rich as the UI version. > > My experience is that this doesn't work. As I remember, PackageMaker > crashed. > -Rick > _______________________________________________ > 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/eclemmer%40rosettaston… > om > > This email sent to eclemmer(a)rosettastone.com _______________________________________________ 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: Keeping a Folder's icon with packagemaker/installer (SOLVED) (PAINFULLY)
by Philip Aker 08 Dec '08

08 Dec '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On 2008-12-07, at 20:42:33, Russ wrote: Philip Aker echo astwta@lvpc.dslh@nl | tr a-z@. p-za-o.@ Democracy: Two wolves and a sheep voting on lunch. _______________________________________________ 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.… OK, this is really and officially a pain in the hindquarters. I'd rant here about the stupidity of it all and why it should be fixed, but obviously Apple doesn't have anyone working on Installer or Packagemaker to read it. I agree these items currently have a lot of problems but the location for bug reporting is at: <https://bugreport.apple.com>. Packagemaker does not preserve the resource forks any more, if it ever did. Thanks for mentioning that. I think I did a package with 3.0 which installed a plugin with a custom icon. At the time there was a warning about some problems for 3.1 so I decided to use the older version. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Keeping a Folder's icon with packagemaker/installer (SOLVED) (PAINFULLY)
by Russ 08 Dec '08

08 Dec '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=ewdikcrWmTTNtbkaN1dfc0z3/DrSHyW7DfZr6KEB/GlhN3D/a1WO8aoIzAJjhklrt3HKR8NURBFbH+07SDm7i+YmAXEG8V3kOLlWfEM/73rHmY4kvRXTAsrSClPgkutdH0JsZZXeiuNkDTUCIV/sds8ohb+hh4/I/hvq34Pb6P4=; OK, this is really and officially a pain in the hindquarters. I'd rant here about the stupidity of it all and why it should be fixed, but obviously Apple doesn't have anyone working on Installer or Packagemaker to read it. Maybe I can save someone else from further time-wastage. Packagemaker does not preserve the resource forks any more, if it ever did. You get a zero-length plain data file. Here is what is necessary: I'm assuming you've manually set up the desired icon on your folder(s), and that you are copying from the where-built-and-installed location to a separate folder structure from which you will make the package. We'll mess with that copy to get the icon to come out right. In your build process, use ditto to build an archive, something like this: -------------------- cd "$the_folder_in_your_package" ditto -c "Icon"$'\r' Icon.cpio rm "Icon"$'\r' -------------------- I'm not sure how well this will transmit through the mailing list, but note there's some bash gimmickry to be able to create the file name with the return in it. Using ditto is a good idea because it will unpack the archive appropriately whether the target volume is HFS+ or unix-style, and it is present in the vanilla Leopard installation. Have the Icon.cpio file installed by your package, along with the setHasCustomIcon program below. Make sure that when you configure ownership and permissions in your package as it is being built, you keep the setHasCustomIcon program's executable bit turned on. You need a postflight install script, something like this: ---------------------- #!/bin/csh # $0: script path; $1: package path; $2: target location; $3: target volume cd /tmp # failsafe cd "$2/Applications/yourApp" ditto -x "Icon.cpio" . ./setHasCustomIcon ../yourApp rm setHasCustomIcon Icon.cpio --------------------- In my postflight script, I also reset the ownership and permissions of everything, since packagemaker messes them up for some customers. Don't forget to put the postflight script into the resources folder of your package, and include it on the scripts tab of your package in packagemaker. setHasCustomIcon.cpp (note that file functionality isn't required) -------------------------- #include <stdio.h> #include "CoreServices/CoreServices.h" // Micro-program to turn on the "has custom icon" bit for a file or folder // files are made invisible too --- assumed to be on the actual icon // One argument in argv[1]: the name of the folder to be modified. // Compile with: gcc -arch ppc -arch i386 -o setHasCustomIcon setHasCustomIcon.cpp -lstdc++ -framework carbon int main(int argc, char *argv[]) { OSErr err; Boolean isDir; FSRef fsRef; FSCatalogInfo catInfo; FolderInfo *folderInfo; FileInfo *fileInfo; // Open the file/folder if (argc != 2) goto bail; err = FSPathMakeRef((const UInt8*)argv[1], &fsRef, &isDir); if (err != noErr) goto bail; // Get finder catalog info err = FSGetCatalogInfo(&fsRef, kFSCatInfoFinderInfo, &catInfo, 0, 0, 0); if (err != noErr) goto bail; // Turn on the custom-icon bit if (isDir) { folderInfo = (FolderInfo*)catInfo.finderInfo; folderInfo->finderFlags |= kHasCustomIcon; } else { fileInfo = (FileInfo*)catInfo.finderInfo; fileInfo->finderFlags |= kHasCustomIcon | kIsInvisible; } // Save the modified attributes err = FSSetCatalogInfo(&fsRef, kFSCatInfoFinderInfo, &catInfo); if (err != noErr) goto bail; bail: return 0; } ------------------------------ Wasn't that fun? It's nice we all have time to play. ----- Original Message ---- To: Installer-Dev mailing-list <installer-dev(a)lists.apple.com> Sent: Sunday, December 7, 2008 4:19:44 PM Subject: Re: Keeping a Folder's icon with packagemaker/installer On 2008-12-04, at 21:29:15, Russ wrote: > Is there a way to get the installed folder's icon set up right, either by installing the Icon? file correctly or some other (simple) method? Adobe CS3 and Snapz Pro X have got it working somehow. I'd just as soon NOT have to create some (Carbon AE) program to go do this programmatically as a post-installation hack. Thanks. It might be possible to specify a pre-existing "Icon\r" file to be placed in your folder. Then the only code you'd have to take care of is setting the custom icon bit on the folder. It's only a few lines using FSSetCatalogInfo() and FSSetCatalogInfo(). Apple has some (really old) sample code at: <http://developer.apple.com/samplecode/SetCustomIcon/> Philip Aker echo astwta@lvpc.dslh@nl | tr a-z@. p-za-o.@ Democracy: Two wolves and a sheep voting on lunch. _______________________________________________ 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/matchmovie%40yahoo.com This email sent to matchmovie(a)yahoo.com _______________________________________________ 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: Keeping a Folder's icon with packagemaker/installer
by Philip Aker 07 Dec '08

07 Dec '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On 2008-12-04, at 21:29:15, Russ wrote: Philip Aker echo astwta@lvpc.dslh@nl | tr a-z@. p-za-o.@ Democracy: Two wolves and a sheep voting on lunch. _______________________________________________ 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.… Is there a way to get the installed folder's icon set up right, either by installing the Icon? file correctly or some other (simple) method? Adobe CS3 and Snapz Pro X have got it working somehow. I'd just as soon NOT have to create some (Carbon AE) program to go do this programmatically as a post-installation hack. Thanks. It might be possible to specify a pre-existing "Icon\r" file to be placed in your folder. Then the only code you'd have to take care of is setting the custom icon bit on the folder. It's only a few lines using FSSetCatalogInfo() and FSSetCatalogInfo(). Apple has some (really old) sample code at: <http://developer.apple.com/samplecode/SetCustomIcon/ > This email sent to site_archiver(a)lists.apple.com

1 0

Re: Keeping a Folder's icon with packagemaker/installer
by Russ 07 Dec '08

07 Dec '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=MbUvohEjRhTcXTnIkQooUzx1U88yjHKYOpKLqiuilYZACaVO10E41d9jlC4g71m2og8P3ruSvcxKHbWxPDHA0usrhUcEzq0RgmBxIAAYRAYQSWCs4ENqbYXCrpdMTBjhN+8lg1L7M499MLZEusbGsmpnnjrOqRZtUaVePmNl/i4=; Unfortunately, adding the extra level of folder does not help. It looks like Installer.app just does not know how to turn back on the custom-icon attribute bit. >From the SetFile man page, even though SetFile is in /usr/bin/SetFile, it is present only if developer tools are installed? I guess none of this is necessary to run iTunes. ----- Original Message ---- Sent: Saturday, December 6, 2008 10:30:30 AM Subject: Re: Keeping a Folder's icon with packagemaker/installer On Dec 5, 2008, at 6:29 AM, Russ wrote: > Battling packagemaker 3.0.1 (172) > > The contents I am installing is a folder into /Applications, my app bundle sits in that folder along with the help files. (I am simplifying to reduce techsupport volume). This setup is routine for 3rd party apps, so I am going with the flow. > > The problem at hand is that I have set up, using Finder, my icon on my top-level folder to make it easier to find in the Applications list. This results in an Icon? file being created in the folder. After digging around a while I've seen the actual required name is something like \pIcon\r and this file is size 0 with the icon in a resource fork! (I guess a plain hidden .folder.icn file would have been too easy?) > > It appears that packagemaker or installer choke on this file, it shows up at the installation, but without the resource fork, extended attributes, and possibly without the special-character name, and of course it does nothing. > > Is there a way to get the installed folder's icon set up right, either by installing the Icon? file correctly or some other (simple) method? Adobe CS3 and Snapz Pro X have got it working somehow. I'd just as soon NOT have to create some (Carbon AE) program to go do this programmatically as a post-installation hack. Thanks. AFAIK: If you set your payload root like this: Payload > My Folder and set the default destination to be '/Applications', you may face this issue. The fact is that SplitForks does not produce the same result twice in this case. If you set your payload root to be like this: Payload > Applications > My Folder and set the default destination to be '/', this issue will not occur. > PS: It is a known bug that Packagemaker likes to turn "Allow Relocation" > back on by itself, right? Pretty sure that's what happens. And that if > it is on, and the user has dragged the old version of your app to the > trash, Installer will (re)install the new version into the trash can, > right? It is a known bug. Not sure if it also applies to the Trash can though. _______________________________________________ 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 packages] Build issue with preinstall/postinstall scripts in PackageMaker 3
by Iceberg-Dev 07 Dec '08

07 Dec '08

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=/EVnOii+9fmr5nsHTQ+/ulgnNA7UyxnH0b6DN5s6I7k=; b=YFquRKkK6v3Uo8sQkBKZddLiUOrcvtJVzu0B4IRdJE7MsrUnfYZuln42Nd9Y2Pgti+ kQ59jgvEqW6HvHQrHy1gIAY9FsxfCo6SjSiXBlPu5HZ4kUj7t13On0DW04kmTmhnPKAz w1tv6HL7g6J27v0AoLGaFxv3Fio0XoiejgP/M= 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=euJUXEs7MpeA7qlqXLjNkT63memT8pwR3RR5DknL58SljbgGvMLCuxRCzheIvnfCxV oVjdyA0MpmA8rLZTQqGey2KyddgDhjjiTiGkK97q6JFIRgCpc0QRnjAZsT13q0quldlb XScIYTVw+UX7irqxsGlQz+pGShiHQb8l7C9K0= Build weakness: --------------- _______________________________________________ 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.… When you build a Flat package, you can specify additional resources and postinstall/preinstall scripts. If your resources folder contains at its first level a file named 'postinstall', and you set a postinstall script, your post installation script will be replaced by the file from the resources folder. Not a common case, but still a bug and potential issue as it's not the script you think you were using that will get run. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Keeping a Folder's icon with packagemaker/installer
by Iceberg-Dev 06 Dec '08

06 Dec '08

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:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=pCsDDh9lGs+34j3wfIQ/mcd78kqzDRSXchTphIGSBws=; b=BB0WXR31LBHlpnjizqDzulxvKYqdwJNSk/sHwW7ddgYAHLchKJzE81PvTAtJN2UTnP /jQ2SWUaWNJy/WSnUkEuKLAP2H3Wc0bdI9bRYoTuCIXmbTncuA3SQBaQ9NoBi/RaYGjq W7KaOudyJylRoVFJoGB1LwwB39A4nheeY8YqE= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=LSmdKNYAY8oYDAZDK+cZKQBGfU/d1OHepVcUa7pR7Nq3W+Sq1Y0uxiuBsp6LHGSJsC 9Tf9iqL1jrNyssotnmHyQMC4tAmsjLcWmIYtuM+sW0DDAJaNrZotDKdwHcM5Vm/xKnwZ EZeYGGsA3fwTQ3g3HJoXy4dZAfXhpLJEpSTm0= On Dec 5, 2008, at 6:29 AM, Russ wrote: Battling packagemaker 3.0.1 (172) AFAIK: If you set your payload root like this: Payload > My Folder If you set your payload root to be like this: Payload > Applications > My Folder and set the default destination to be '/', this issue will not occur. It is a known bug. Not sure if it also applies to the Trash can though. _______________________________________________ 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.… The contents I am installing is a folder into /Applications, my app bundle sits in that folder along with the help files. (I am simplifying to reduce techsupport volume). This setup is routine for 3rd party apps, so I am going with the flow. The problem at hand is that I have set up, using Finder, my icon on my top-level folder to make it easier to find in the Applications list. This results in an Icon? file being created in the folder. After digging around a while I've seen the actual required name is something like \pIcon\r and this file is size 0 with the icon in a resource fork! (I guess a plain hidden .folder.icn file would have been too easy?) It appears that packagemaker or installer choke on this file, it shows up at the installation, but without the resource fork, extended attributes, and possibly without the special-character name, and of course it does nothing. Is there a way to get the installed folder's icon set up right, either by installing the Icon? file correctly or some other (simple) method? Adobe CS3 and Snapz Pro X have got it working somehow. I'd just as soon NOT have to create some (Carbon AE) program to go do this programmatically as a post-installation hack. Thanks. and set the default destination to be '/Applications', you may face this issue. The fact is that SplitForks does not produce the same result twice in this case. PS: It is a known bug that Packagemaker likes to turn "Allow Relocation" back on by itself, right? Pretty sure that's what happens. And that if it is on, and the user has dragged the old version of your app to the trash, Installer will (re)install the new version into the trash can, right? This email sent to site_archiver(a)lists.apple.com

1 0