September 2008 - Installer-dev

Re: Package maker always looses destination path, often access rights?
by Luke Bellandi 08 Sep '08

08 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckRzDqLgFyjsceyAkefYYa3wjcftg== Thread-topic: Package maker always looses destination path, often access rights? User-agent: Microsoft-Entourage/12.10.0.080409 On 9/8/08 8:37 AM, "Brett George" <brett(a)apogeedigital.com> wrote: > Thomas Engelmeier wrote: >> What triggers the Package Maker amnesia? Is there an known workaround? >> How do you folks create kext installers? > > Package Maker v3 is full of bugs and pretty much useless. I recommend > copying across an old copy from Tiger. Is that right? I find v3 to be quite useful and a massive improvement over earlier generations given its WYSIWIG editor, and UI hooks into almost all functionality provided by the installation packaging and install mechanism on Mac OS X. Maybe you would be so kind as to expand on your broad, yet wholly unspecific, criticism of the product for this list's edification? You might also consider filing bugs on the product with Apple in an effort to help improve the product. - Luke > Brett. > _______________________________________________ > 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/luke%40adobe.com > > This email sent to luke(a)adobe.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

PackageMaker newbie questions
by David Watson 08 Sep '08

08 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com test/ - contains my files to install scripts/ - contains my scripts resources/ - contains License.rtf Distribution (an installer-script XML file) Resources, containing my License.rtf test.pkg, containing what I'd expect I've just started wading into the world of PackageMaker - I've been doing Mac development for a while, but just now started working on packaging. I've been trying to reconcile the Software Delivery Guide with the current reality, since it appears the guide has not been updated for about 2 years. What I've determined is that if I target my packages for 10.4, everything seems to work as I would expect, but when targeted for 10.5, things go a bit off the rails. I understand the different is the new flat package format, which behaves rather differently from bundle- based packages. The PackageMaker GUI seems to be horrendously broken as of version 3.0.2, and I prefer to script my builds, so I've been using the command-line. It appears that if you build a flat package from the command line, it implicitly creates a distribution package, completely with distribution script. I haven't figured out how to convince it to use my Welcome and License files, so I'm wondering if there is some additional magic. Here's my structure: If I run: /Developer/Applications/Utilities/PackageMaker.app/Contents/ MacOS/PackageMaker -v --root test/ --id com.example.testpkg --version 1 -s scripts/ -e resources/ --out test.pkg This produces a bundle-style package, working as I would expect. If I add --target 10.5, however, that's where things go weird. When I run this, it ignores my License.rtf, although I can see it is included in the package. Running pkgutil --expand shows me that the test.pkg actually contains: Is there any way, when targeting 10.5, to have it *not* create a distribution metapackage? Also, is there any documentation on the PackageInfo file? Alternatively, is there a way to build a pmdoc that simply references packages that I've built separately? It looks like there should be, in theory, by using "Add Package Reference", but that just seems to be horribly busted. _______________________________________________ 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: Package maker always looses destination path, often access rights?
by Brett George 08 Sep '08

08 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.16 (Macintosh/20080707) Thomas Engelmeier wrote: > What triggers the Package Maker amnesia? Is there an known workaround? > How do you folks create kext installers? Package Maker v3 is full of bugs and pretty much useless. I recommend copying across an old copy from Tiger. Brett. _______________________________________________ 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

Package maker always looses destination path, often access rights?
by Thomas Engelmeier 08 Sep '08

08 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi, TIA, Tom_E I'm creating some installer for an USB device that requires an daemon and some kexts. Currently I'm fighting with package maker 3.0.2. If I read the (sparse) documentation correctly, instead of one Package starting at / with a root directory containing /System/Library/Extensions and /Library/Application Support, I should use subpackages for each folder (implicit consequence of "don't create standard system directories with your package") The problem is, I can not get the destination directory to stick. Even with an fresh created package, one content folder and an destination directory set, the dest dir ist lost if I save and reopen. The second problem is most times after an save and reopen my kext access rights are reset to 664 - rendering the installed kext unusuable. I adjusted the orginal kext file rights + owner to the desired result, used Package Makers UI, and still they become group writable after saves and reopening. What triggers the Package Maker amnesia? Is there an known workaround? How do you folks create kext installers? _______________________________________________ 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 Requirement
by Stéphane Sudre 05 Sep '08

05 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 5, 2008, at 8:45 PM, Steven J. Vogt wrote: Greetings Stéphane! Yes, you can use shell scripts. The 3 things to do are: - include the script in the distribution - build then check that: 1. The script is correctly included in the distribution _______________________________________________ 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.… Sorry it took me so long to get back to you. The script worked perfect! It does exactly what I need it to do. I didn't realize until now, that I could use other forms of scripting to? I'm good with shell scripting, so I maybe wrong in saying this and haven't tried, but maybe I could have used a shell script if is supported? - call the script through the appropriate requirement (system.run ("MyScript.pl") for instance) 2. The allow-external-scripts option is set to 'yes' (on PackageMaker 3.0, it was never set. I tend to remember it has been fixed in 3.0.1 but I'm not running on Leopard at the time of this writing so I can't confirm). This email sent to site_archiver(a)lists.apple.com

1 0

RE: Windows Safari Install location
by John Pfeiffer 05 Sep '08

05 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckO85mNnr3XHBUQQhyNeTsXzdFU5wAoJBpQ Thread-topic: Windows Safari Install location _______________________________________________ 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 Requirement
by Steven J. Vogt 05 Sep '08

05 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Greetings Stéphane! Thanks a lot for the great advice! Steve On Aug 31, 2008, at 9:54 AM, Stéphane Sudre wrote: On Aug 30, 2008, at 11:44 PM, Steven J. Vogt wrote: Greetings! /* This version will check only the system volume */ function myRequirementFunction() { var tResult = false; return tResult; } /* This version will check the different volumes */ function myRequirementFunction() { var tResult = false; try { var tMountPoint; tMountPoint=my.target.mountpoint; return tResult; } -- STephane _______________________________________________ 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.… Sorry it took me so long to get back to you. The script worked perfect! It does exactly what I need it to do. I didn't realize until now, that I could use other forms of scripting to? I'm good with shell scripting, so I maybe wrong in saying this and haven't tried, but maybe I could have used a shell script if is supported? I am currently trying to distribute a package that adds printers to student computers. So far I have it accommodating for Tiger and Leopard differences in where the PPD's live. This is in one installer and it's is working great. What I'm trying to do now is check if a certain PPD file exists and if it doesn't I want to not allow the installer to run. I looked at setting a requirement for the package "If file exists" I could then specify the file. What I really need to do is check if one or the other file exists. (PPD on Tiger or PPD on Leopard). I can't figure out a way to check multiple files and continue if one or the other is found. Any ideas would be greatly appreciated. I know I could split the package into to, but I'm hoping to be able to keep in one package. If you're targeting Tiger or Leopard, I would assume you're using a distribution script. If this is really the case, there is nothing preventing you from writing your own javascript function for the requirements. try { tResult = system.files.fileExistsAtPath('/The/Path/To/My/File') == true || system.files.fileExistsAtPath('/The/Path/To/My/File') == true; } catch (tException) { } AFAIK, it could be improved with something like this since you're saying the PPD is not at the same location depending on the OS version. /* If the path has again changed in Snow Leopard, you would need to add another test */ if (my.target.systemVersion.ProductVersion >= '10.5.0') { tResult = system.files.fileExistsAtPath(tMountPoint + "/The/Path/ To/My/File/For/Leopard"); } else if (my.target.systemVersion.ProductVersion >= '10.4.0') { tResult = system.files.fileExistsAtPath(tMountPoint + "/The/Path/ To/My/File/For/Tiger"); } } catch (tException) { } This has been typed in Apple Mail and I'm not a Javascript expert so this may not work. This email sent to site_archiver(a)lists.apple.com

1 0

Re: how to hide the static text in the left the main window during installation.
by Luke Bellandi 05 Sep '08

05 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckPdADAlFRsNMLEg0e+OYem4qijfw== Thread-topic: how to hide the static text in the left the main window during installation. User-agent: Microsoft-Entourage/12.10.0.080409 On 9/3/08 2:26 PM, "Stéphane Sudre" <iceberg-dev(a)orange.fr> wrote: > > On Sep 3, 2008, at 10:52 AM, XiaoGang Li wrote: > > - trust Installer.app to skip the Destination Select pane if you set > the distribution to install on root volume only (sometimes it works > on Leopard, sometimes it doesn't but it's a bug AFAIK). This bug is due to a timing issue. Installer.app scans the disks and if it's finished doing so by the time the user gets to the Destination Select pane, that pane will be skipped, otherwise the user will see it. - Luke _______________________________________________ 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

Windows Safari Install location
by John Pfeiffer 05 Sep '08

05 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AckO85mNnr3XHBUQQhyNeTsXzdFU5w== Thread-topic: Windows Safari Install location _______________________________________________ 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: how to hide the static text in the left the main window during installation.
by Stéphane Sudre 03 Sep '08

03 Sep '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 3, 2008, at 10:52 AM, XiaoGang Li wrote: Something that would be close to this and which is supported is to: - use the customize options with the never value. This would give: <options customize='never' rootVolumeOnly='true' /> This is not an exact match for your needs 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.… Hi, list, As we know, the normal installation order is like this: Introduction->License->Destination Select->Installation Type- >Installation->Summary, but this time, I want to jump over the "Destination Select" and "Installation Type", I mean after user checking the license, the installation window enters into installation phase directly, no Destination select and no installation type. (Sorry, this requirement seems a little unreasoning, but it is my job now,J) In order to implement it, my solution likes this: Add a folder named Plugins into the Contents. And put a single plist file in the Plugins directory, the content of the plist file like this: ………… <dict> <key>SectionOrder</key> <array> <string>Introduction</string> <string>ReadMe</string> <string>License</string> <string>Install</string> <string>Summary</string> </array> </dict> And luckily, the two unspecified installation phase UI in this plist file do not appear. But I noticed that there are static text lists on the left of the main window, which used to show the progress update for user. So, my question is coming: Even I do not specify the other two phase into the order list, I still can see their titles on the left of the main window, looks like this: l Introduction l License l Installation l Summary l Installation Type l Destination Select. And I wonder it is should be hided in the main window, because I can not enter into this phase UI actually. So, do you have any solution to hide the static text field? Or someone give a better solution? Thanks very much. Hmm... This is not a supported solution I think. Removing Installation steps using the SectionOrder array proved to cause issues during the installation process in the past. - trust Installer.app to skip the Destination Select pane if you set the distribution to install on root volume only (sometimes it works on Leopard, sometimes it doesn't but it's a bug AFAIK). Otherwise, a solution could be to use your own front-end and call the installer command line tool. This email sent to site_archiver(a)lists.apple.com

1 0