August 2009 - Installer-dev

Re: Command-line version of PackageMaker v3
by Jim Dodd 07 Aug '09

07 Aug '09

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=yahoo.com; s=s1024; t=1249678713; bh=sDWRFjyoWHL5fpIUIxuZ+PTrUqUjFU513huQ0h8Xj9M=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=v/X+BNPCtmhRUOCfUte6GZa3Z+CykDmKPO4ALcFrD4nzcfmrHUrzaV6qOlLTL2OfPEgq7UytKn26VkdBqM4UJ6/ws7HUDHINbSjnvw8U7mqv1kiFmXtkIsozV8ov6vUnSzn5mLnpwVXpCVzNE49qyRuxyjWrA+iVJdstFK3bXqo= Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=JovLh/gmgycr+CqwfPJQWSfFRPGqEKZ0YWj/KDZ4O8kcTErMN1VaZBAWxtkXnkyg1m8FLVovlj7+1sRsVuw+rw2ExltnjQx+jkDbjoiLbqdJ8jJqSn8Fmkj9RzVhXYeNWsxUMHT1oFGQhkLY1UfotKysGPJ+C1CGU+Go3/sA4aY=; _______________________________________________ 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:Command-line version of PackageMaker v3
by Carl Harris 07 Aug '09

07 Aug '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.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

Command-line version of PackageMaker v3
by Jim Dodd 07 Aug '09

07 Aug '09

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=yahoo.com; s=s1024; t=1249670414; bh=TM+So18JAhFjO+yjZ1T6FXMKlM7QM+SaviyUcQVW2SA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=ciNG7SYrCxR8ZPJyi0wg5PdXOa63ulfQF5y1HSih4K95orS2XU7uR2kyY2OizFrSCQKxVv5ENySEHMT+dTg8wD9NbQj7Br0BOCSSvNou4rH6zU0LmHtE/Mjkgfygnmxby2whA5171HHorQ/cJ73dWQU2IX1k7PJf7meaRnGx0bg= Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=j3PP5WrGxIyn0RxEAGQCzFRt7ZziL4Ecwt8V0MeI+LS28YfALEBkxlz/9yuh50VozCmv5rMwud8HsYEFHdl4tdhoH/f6cF8g9yHr/0G8EwIjCpnUru2tKC5lIDkvjlIBqiWp1gNJwHbPxARclNT/Y4kJLG/AQ5GuRRdS/+5mRGM=; I have switched from using PackageMaker v2 to PackageMaker v3 and I'm having a few problems. I can get the installer we want in the GUI version of PackageMaker but we need to automate the making f our installer and I need to use the command-line version of PackageMaker. I would like to use the PMDOC created by the GUI version in the command-line version. But everything I've tried with that causes PackageMaker to crash with an NSInvalidArgumentException. Yet if I run the GUI version from the same PMDOC file, it works. In case it offers any clues, here is the command-line I use for this: packagemaker --doc OurApp.pmdoc I realize that doesn't help much because everything is in the PMDOC. But, as I said, if I open that PMDOC in the GUI version, it creates a valid, usable installer package. The other option is to run the command-line version without the PMDOC input. I can get this to work but it defaults to including a TokenDefinitions.plist file in the Contents/Resources folder that is set up to use CommonAppSearch (whatever that is, it doesn't match any of the options in the GUI version) which ends up "upgrading" the development versions on our machine when the app isn't in it's default location. Is there some way to specify the search method from the command-line? I don't see an option for defining the contents of the TokenDefinitions.plist file. I am using this command-line: packagemaker -r "./Distribution/Package_contents" -f PMInfo.plist -o OurApp.pkg -n 3.0 -t OurApp -e ".Distribution/Install_resources" -s ".Distribution/Install_resources" -h system -b -v where Package_contents has our application and help files, Install_resources has our Welcome, ReadMe, License and pre- and post-install scripts. Thanks for any help you can offer. Jim Dodd Onset Computer Corporation _______________________________________________ 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

custom backgrounds in only *some* dialogs?
by Howard Moon 07 Aug '09

07 Aug '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi all, Thanks, Howard _______________________________________________ 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 any way to have our custom background only show up for *some* dialogs? It's annoying to have an image behind the scrolling text of the license, for example (even though we've made it so it's a ghost-like image of our logo). And the tiny amount of space at the bottom left isn't really suitable for our logo. I've messed around a little bit with an installer plugin, but have not yet found any documentation describing how I might create a dialog and insert it in the install sequence. (The default installer plugin, when added to my installer, simply shows a view on top of one of the existing dialogs in the sequence, not a separate window.) On a more general note, is the apparent inability to add or customize dialogs in the installers a function of the Apple installer app, or just the tools (e.g., PackageMaker or Iceberg)? If it's just the tools that are limiting us, is there any good documentation on how to assemble a package for installation that includes additional and/or customized dialogs? If so, I could probably put together my packages manually, since they're all identical except for the plug-in being installed. Is there anyone out there who's making package installers and does *any* customization? Is there any documentation on how to go about it? Or am I stuck with VISE-X? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Package Maker background color
by Rusty Myers 07 Aug '09

07 Aug '09

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:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4iFRQx4U11v1G8MICJ62TP7Bttj+BQjNoisYl8Cl7aI=; b=ILk6+AK8oDO0YHstUh24bJ3KeC2C4noKW1qQ8d3QqFeJB2/FCygaqwlGLIs5cLdaBc USr0aj7bmpak+slsjhMoHkI1onInrR/GcOIRzxytqZd7bEmJ96N+RKqsoqI4e+tkIxYG 5+ZnNgIfpvklcrAvWypUfTsO8xqLEjby41WJI= 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:content-transfer-encoding; b=D191NylSfwUQtkqYCFzfmEkiN87PeEe0fFtdD/XAoG1hhDtgJtjsvhfnAP3S/kYl/f K1aDxg2Op3OeuiXZk2ZSApaRAfovb3UTCRhfo4lDezTIW1g7voDXUep1jPOJRHGu/32s NlDYy+WuZsmsbw558nvd+qNEA5U8N/9ejMQTI= This site has a good picture with the measurements http://s.sudre.free.fr/Stuff/PackageMaker_Howto.html On Fri, Jul 31, 2009 at 12:54 PM, Tim Murison<tim.murison(a)radialpoint.com> wrote: > Hi, > > I am setting a background image to my installer packages. Sometimes the > installer resizes its windows and when this happens, I can see the > background color which is not the same as my image. > > Is it possible to set background color in Package Maker, if not, what size > do I need to make my image to ensure that it will always cover the entire > background of the installer window (I do not want to it stretch out of > proportion). > > -Tim > > > > *********************************************************************** > > This e-mail and its attachments are confidential, legally privileged, may be subject to copyright and sent solely for the attention of the addressee(s). > Any unauthorized use or disclosure is prohibited. Statements and opinions expressed in this e-mail may not represent those of Radialpoint. > > Le contenu de ce courriel est confidentiel, privilégié et peut être soumis à des droits d'auteur. Il est envoyé à l'intention exclusive de son ou de ses > destinataires. Il est interdit de l'utiliser ou de le divulguer sans autorisation. Les opinions exprimées dans le présent courriel peuvent diverger de celles de Radialpoint. > _______________________________________________ > 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/rustymyers.lists%40gma… > > This email sent to rustymyers.lists(a)gmail.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: Package installation check...
by Rusty Myers 07 Aug '09

07 Aug '09

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:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=DU6Wg6JYnQcpE2YBJHbGW6Q1i6pDw4+4kh4PGNsj45E=; b=pqrY6rXu2Od+UKNda2E1TFDSRXlOCVQhC0mimAk9kiK2R/bH0XUnmGegXodJL1RdYr Ev+BdpjByObpEpoRkne24gNjTvjZ4+mtmVbpXkj+GwJQRW8tz3kneQbqloB+OoZwBDWv irpLLDE6wx8RTavEb9v0KXpyx9Hn4kbZtgmsU= 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 :content-type:content-transfer-encoding; b=Q6DWZ1cXjD6IPIaWy4kXpM0oEdq72IUuxzEAbkQm2y6K0fnduASYU6T+T4mYC7WuiT y9wE01XwGbH3mevhVOHfxY6bAzsKc/ZkyLhnlXi5UwmASG2TCpxyF4V+xxr07ThLwm0q W6eDWpku8X/v7MdjN62XTfCAXDfOpOgxT18+8= Are you trying this from the command line or the GUI? You can set some requirements from the GUI. You could also run a preflight script and exit 1 if your requirements are not met. I think that should exit the package with a fail. On Thu, Jul 30, 2009 at 7:41 PM, Charles E. Heizer<heizer1(a)llnl.gov> wrote: > Hello, > I would like to know if it's possible to run through the Installation > checks on a package to see if it can even be installed on a system? > > For example, I have created a Test distribution package which I know > will fail, it's requiring >= 20 CPU's. I would like to run a command > from the command line to see if this package is applicable to this > system. > > I have played with installer using the following args (-dominfo - > volinfo -pkginfo) and they all come back with valid info but none of > them seem to run the requirements to tell me that it wont install. > > > Thanks, > Charles Heizer > > > > > _______________________________________________ > 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/rustymyers.lists%40gma… > > This email sent to rustymyers.lists(a)gmail.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: Custom dialogs in PackageMaker?
by Greg Neagle 07 Aug '09

07 Aug '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Aug 6, 2009, at 1:42 PM, Howard Moon wrote: You skip them. -Greg _______________________________________________ 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.… good points all, but our software is not something that is generally installed by system administrators, Hmm. I've had to wrestle a lots of audio plugins for ProTools machines. I'd much rather use the same system I already use to manage installs than have to visit the user and do a manual install. It's more likely the machine will get timely updates of the software if I can use my normal methods of installation. or in the background. (How would you handle the "normal" dialogs, like the license file and acknowledgement, read-me, etc., if run that way?) They're audio plug-ins (and supporting documentation files, etc.), and they run inside audio hosts. We need to be able to run an authorization application at the end of the installs to make it easier for users to authorize their software, and we can't do this from within the hosts. So, prior to running the authorization app, we display a message that says that the installation has completed and that the authorization app will run when they hit Continue. When run via command-line, you'd skip this, and the administrator would be responsible for running the authorization app separately. It's laudable to make things easy for the average end-user doing a manual install, but don't make it impossible for an admin to do an automated/remote install. This email sent to site_archiver(a)lists.apple.com

1 0

Skipping Select Destination step
by Chad Armstrong 07 Aug '09

07 Aug '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Regards, Chad _______________________________________________ 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 creating a package (whether it be a standard package, metapackage, or distribution package), is there a way to completely bypass the Select Destination step? I want to be able to install my files on the root volume and do not want to give any indication to the user that the application can be placed anywhere else. Ultimately, I'd like to stream line the installation process as much as possible by reducing any unnecessary steps. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Another Iceberg question
by Iceberg-Dev 06 Aug '09

06 Aug '09

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=cDpQ6UZRAdTjMjzZhk4z7mRp63a/eOL+eI7dtN5JOYo=; b=lECr2gm2tlnxpasLi23lpeudoREIJ0Vsx06g66i6uiExExL0Y9ISI1KRFTm1SIYYwN OwsepKk/Qfe/rpKSBzBkL1MwV+Y7/TYujnP7ZGCs/TgHLUSBvbiGK8T04+vGHEgpo+9Y 6q9FpGOU1cFHqG2jz/SKrMXfvhPuzgEKmPdXQ= 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=OQZgx7IyYEXILLveJJSOTnhcztgftfarJ6UckxHF/jXDgF7l90KHnH48pVUf7aiOL/ xw5HzE/b+EPh5QtCyPay4QOG2L7NaMDGAN9FoxqT40qNlmTeT6uWKHF4uaNNlb/d8dNL OYzHY9YbbZLMPE9lO2XrH7P2b2C1ZR+ORduuk= On Aug 6, 2009, at 8:31 PM, Howard Moon wrote: Hi again, <key>IFPkgHideSubpackages</key> <true/> This would require editing the Info.plis file. _______________________________________________ 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 to be such a pain, but does anyone know if there's a way to make Iceberg-built installers only allow the "Standard Install" option? All my components are Required components, so I'm surprised that it shows the "Customize" button when running the installer. Since there's nothing to Customize, is shouldn't show that button, but I can't figure out how to hide it. (In PackageMaker, there's an option for that.) The Standard Install Only mode is available for Distribution [Script]. It's only supported by PackageMaker 3 (version 2 also supports it if you're a thrill seeker). There's an undocumented feature to make it work on Mac OS X 10.4 and later for non distribution script but it's not recommended. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Custom dialogs in PackageMaker?
by Howard Moon 06 Aug '09

06 Aug '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thanks, Karl, Thanks, -Howard On Aug 6, 2009, at 11:23 AM, Karl Kuehn wrote: On Aug 6, 2009, at 9:15 AM, Howard Moon wrote: So a few notes about this: _______________________________________________ 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.… good points all, but our software is not something that is generally installed by system administrators, or in the background. (How would you handle the "normal" dialogs, like the license file and acknowledgement, read-me, etc., if run that way?) They're audio plug- ins (and supporting documentation files, etc.), and they run inside audio hosts. We need to be able to run an authorization application at the end of the installs to make it easier for users to authorize their software, and we can't do this from within the hosts. So, prior to running the authorization app, we display a message that says that the installation has completed and that the authorization app will run when they hit Continue. In VISE-X installers, this is easy-peasy. In PackageMaker, I tried using the Finish Up dialog for this (or whatever it was called), but when I do that, the post-flight action to run the authorization app executes before that screen is displayed. I need to display the message, wait for the user to acknowledge it, and then run the app. I really have no choice here. I guess I'll have to look into pkg plugins, then. (Are they easier to add to Iceberg than to PackageMaker?) I'm new to this list and to PackageMaker. I've been using VISE-X, and one of the things we do often is to add a custom dialog to the installation. I can't find any way to do this using PackageMaker. Overall, it seems like a much less useful tool than VISE-X (although it's free, so that's something!). Is there a way to add custom dialogs in PackageMaker? 1) You can create pkg plugins that can have custom dialogs, etc. You will have to do a little work, but it is not that tough. 2) You could put GUI things into scripts, but this is a really, really bad idea (see item 4). 3) I have rarely seen things that actually need custom GUIs. Most things will work with a thought-through custom package choices page. The only exception I can think of is EULA pages, and that is already part of the installer. 4) As a system admin I will STRONGLY caution you to rethink that putting custom dialogs in and installer, for all the same reasons that make VISE hated by system administrators: - Your installers will be used in situations where the person doing the install is not at the computer, and has no access to the GUI. Here I am talking about ARD installs, automated imaging systems, and the like. If you try and put up a GUI your installer may hang. These sorts of systems are becoming more wide-spread. And do you really want to get lumped in with Adobe in hatred by admins? - Installers run in the background that pop up messages will surprise users who may not know (or care) that IT is installing things/updates on their computer in the background. - Your program should more properly take care of anything you would do in an installer on first-run (or better yet: whenever it needs the information). Putting things in the installer only means that you can't correct them later. Remember: users of your product might not have access to the installer (that might be in the hands of IT). I've also heard about a free program called Iceberg. Is that something that might be more useful than PackageMaker (in Leopard)? Can custom dialogs be added in that software (easily)? Iceberg makes .pkg's, just like PackageMaker. So the outcome is going to be identical to 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/howard%40antarestech.c… This email sent to howard(a)antarestech.com This email sent to site_archiver(a)lists.apple.com

1 0