March 2010 - Installer-dev - lists.apple.com

Re: Removing the Installer Dialogs in Packages
by Don Montalvo 05 Mar '10

05 Mar '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:references:in-reply-to :mime-version:content-type:message-id:content-transfer-encoding:cc :from:subject:date:to:x-mailer; bh=d6C93aYTkA/0R9OEAkMjcStzt/U+Zrf08LDiTApTE5s=; b=q9+XhNLNxukWkqfkUfS8OoNNUmgIsUZvVKNT3quWBLbmnr9+wm9tTr7uU73EZ2vxVn fiVIZkbYZOUUGqddEmTbgtk6cHkai3p6SeKMSfe0ybHsyhyLLUX1PR8sz1GHqQgmLKVC mCrNXtNEk5LAmk9bQ/b4OJGODOcumvuRaGXrc= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=HqqfVwJtZMQXH2yblm627qM3jA+y0NjB2v9WbAgbtIv7QHD2HDW9LFp5jQltaYZREn p7LitdzKE8i2DRpJefuFvCeruaLTVLOE4mQgb0fh4sl32h5CmfrrGAxWrHs7BHD3b6gM +KqnQTKidHqKGNNl/SzMBagq2zmawMp7tpG20= Bill Coderre <bc(a)apple.com> wrote: > On Mar 5, 2010, at 10:43 AM, Karthikeyan M wrote: > >> The package we create using snapshot method in Composer normally has following >> >> 1.Welcome Window will show continue button >> 2.Installation type with Install button, >> 3.Authentication Dialog >> 4.progress bar >> 5.The Final Close Window >> >> I have to make two changes (ie) remove the Install Type window and add Install button in the Welcome Screen and finally installer window should close (if possible). >> >> Even i too consider to use Standard Install but our management requirement. :-( > > OK, I'll bite the bait: It would be difficult if not impossible to make the official Apple Installer.app behave in accordance with your spec. > > Run that one up the flagpole and see how it goes. > > I'll leave it up to other people to discuss third-party installer applications. I don't use them. > > My off-the-cuff guess as to how to achieve the result using Mac-standard tools would be to write a program that provides the kind of user experience you specify, then calls the unix command "installer" to do the actual installation. > > IT WOULD BE A NON-TRIVIAL PROGRAM, since it would involve hooking up password authorization, gathering progress information, setting up the Unix launch environment so that existing packages get the environment variables they expect, etc. > > Would end users tolerate such a thing? I probably should not comment. I agree, that default behavior for Apple Installer is probably something that's not safe to futz with (for vulnerability risk management if anything). Just a guess, this may be a request from management with the intent to align with the Wintel side installer behavior? Adobe (CS suite) is a good example of how things can go haywire if one platform's default installer processes are bent to align with other platform processes. It can be quite a management nightmare. :) I am also not a fan of third party installer formats (InstallerVISE, Mindvision, etc.), preferring Apple's standard pkg/mpkg format for distribution. That said, if the environment has Casper, the software is deployable using Self Service. Don _______________________________________________ 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: Background graphics for DMGs (again)
by Paul Sanders 05 Mar '10

05 Mar '10

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

Re: Background graphics for DMGs (again)
by Paul Sanders 05 Mar '10

05 Mar '10

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

Re: Background graphics for DMGs (again)
by Kevin Brock 05 Mar '10

05 Mar '10

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

Re: Background graphics for DMGs (again)
by Paul Sanders 05 Mar '10

05 Mar '10

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

Re: Removing the Installer Dialogs in Packages
by Bill Coderre 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 5, 2010, at 10:43 AM, Karthikeyan M wrote: > The package we create using snapshot method in Composer normally has following > > 1.Welcome Window will show continue button > 2.Installation type with Install button, > 3.Authentication Dialog > 4.progress bar > 5.The Final Close Window > > > I have to make two changes (ie) remove the Install Type window and add Install button in the Welcome Screen and finally installer window should close (if possible). > > Even i too consider to use Standard Install but our management requirement. :-( OK, I'll bite the bait: It would be difficult if not impossible to make the official Apple Installer.app behave in accordance with your spec. Run that one up the flagpole and see how it goes. I'll leave it up to other people to discuss third-party installer applications. I don't use them. My off-the-cuff guess as to how to achieve the result using Mac-standard tools would be to write a program that provides the kind of user experience you specify, then calls the unix command "installer" to do the actual installation. IT WOULD BE A NON-TRIVIAL PROGRAM, since it would involve hooking up password authorization, gathering progress information, setting up the Unix launch environment so that existing packages get the environment variables they expect, etc. Would end users tolerate such a thing? I probably should not comment. _______________________________________________ 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

Background graphics for DMGs (again)
by Kevin Brock 05 Mar '10

05 Mar '10

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

Re: Where do I start?
by Bill Coderre 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 5, 2010, at 9:51 AM, Allan Marcus wrote: > I would like to start to add some JavaScript as a requirements test to my installer. I cannot find any documentation on how to do this. I can find Installer JavaScript References on the Mac Dev web site, but nothing on how to do it. > > Where do I put my scripts? > Are there examples? > is there any documentation at all? Did you see http://developer.apple.com/mac/library/navigation/index.html#section=Topics… ? Most people seem to use PackageMaker, at least to get "the lay of the land." Another popular choice is to take apart existing packages and see what they do. However, let me also give you a thumbnail sketch. Note that this is NOT complete or fully detailed. It's just to help you get your bearings. (Also, with almost every major OS release, there are changes and improvements to package format, but older package formats are still supported and install almost "the same" in later OS revisions. I'll outline the 10.4-era flavor of packages, because 10.4-era packages are a LOT "better" and also much different than previous versions, and chances are you don't have to support 10.3.) 10.4-era installer packages are folders with a .pkg extension, a particular flavor of what Mac OS X calls "bundles." The bundle has a layout that looks like this: Foo.pkg Contents Archive.bom Archive.pax.gz Foo.dist Info.plist Resources preflight postflight English.lproj (other language lprojs) The distribution is documented here: http://developer.apple.com/mac/library/documentation/DeveloperTools/Referen… preflight and postflight are unix executables (I use perl scripts, but you can use sh if you are a glutton for punishment). They need to have the exact name, NO hidden EXTENSIONS, and they have to have the unix executable bit set and the correct ownership and permissions. Installation has a set of steps it goes through: 1) The distribution of the package is run, to see if the installation will be allowed. 2) User clicks install. 3) preflight runs 4) Archives are unpacked and copied into their destinations 5) postflight runs. A very brief note on "metapackages": It is often a good idea to make an installer from several small packages, bunched together in what is called a "Metapackage." For instance, if you want to install an extension only on certain hardware, it's convenient to put that stuff in its own package. Then you have a "head" package containing a distribution and associated user-visible text, and the distribution of this metapackage determines which subpackages get installed. You then put all the packages inside the metapackage, and give the metapackage the extension ".mpkg" The installer runs ONLY the distribution of the head package. The distributions of the subpackages are ignored. However, each subpackage still runs its preflight and postflight scripts. _______________________________________________ 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: Removing the Installer Dialogs in Packages
by Karthikeyan M 05 Mar '10

05 Mar '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:message-id:date:from:reply-to :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=Go32CabnDZ0csG8qzmMgq7p9U4sfgEhRivcnV4M3hIo=; b=DUgi8fZJgjJ9AP2djCRoZM31QRu/ebGVR9ynupqdm7dycMwme6Jnl18eGnIhNoXgLk OLtsCZefrCZ4SI1ORSYXqRszy0M0er5Q/cY5JByDRmDQcgjzz+3ikOEGuIWQIG3aXcGI eC6x/uHnlspWdGYih9HtsGrRaho7JqZzd2nLU= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=M+SEWjJ4KnLNshMKD9BXG+gihDLuOnNYqGb1zOc4HYa01EcDB/BPaso5bBRiFHAOmh s+4SE3eoorgdzOJ5llbOhwqHpa63QPS/n7fKPThUhLDRh9PfxyVqwK0T68ULEZeJbtzk 8pLEpuUYlFaOsD7OEXVKBrzvRYnE7BkVA8sNA= User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 Hi Xochitl, Thanks for the info :-) The package we create using snapshot method in Composer normally has following 1.Welcome Window will show continue button 2.Installation type with Install button, 3.Authentication Dialog 4.progress bar 5.The Final Close Window I have to make two changes (ie)remove the Install Type window and add Install button in the Welcome Screen and finally installer window should close(if possible). Even i too consider to use Standard Install but our management requirement. :-( Regards, Karthikeyan M _______________________________________________ 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 > Hi, > > We have to create a one Click Install Package. Package needs to be as follows > > If users clicks the package file, it should show the Welcome Screen > (Installer) and the same screen should have Install Button. if the > install button is clicked, it should ask for authentication then it > should show the Progress and Finish/Close Window. The total > installation should should only have three user intervention. > > 1. Double-click to launch > 2. First screen (Welcome screen) should show the Install Button > 3. User should get Authentication Dialog > 3. The installer should finish, the window should close automatically > > Thanks& Regards, > Karthikeyan M > You can disable a lot of the extra menus like "choose install location" when using package making tools. The only one I am familiar with is Package Maker.app which I think is a default installed with Xcode. I really recommend against using this tool though if you can find a better one. Package Maker will let you edit settings which it then completely ignores. The Help for it is also really bad. Iceberg was suggested to me, but I haven't gotten the hang of it yet. My package does basically what you are asking for. * Introduction - > click "Continue" * License Agreement * Destination Select -> This is disabled, all they can do is pick "Continue" * Installation type -> Only standard installation is allowed. Click "Install" Program installs and presents summary, followed by another click to close the window. I would consider using a standard, simple package install. Why would you want your Mac OS program to not install like a Mac OS program?

1 0

Re: Removing the Installer Dialogs in Packages
by Xochitl Lunde 05 Mar '10

05 Mar '10

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 > Hi, > > We have to create a one Click Install Package. Package needs to be as follows > > If users clicks the package file, it should show the Welcome Screen > (Installer) and the same screen should have Install Button. if the > install button is clicked, it should ask for authentication then it > should show the Progress and Finish/Close Window. The total > installation should should only have three user intervention. > > 1. Double-click to launch > 2. First screen (Welcome screen) should show the Install Button > 3. User should get Authentication Dialog > 3. The installer should finish, the window should close automatically > > Thanks& Regards, > Karthikeyan M > You can disable a lot of the extra menus like "choose install location" when using package making tools. The only one I am familiar with is Package Maker.app which I think is a default installed with Xcode. I really recommend against using this tool though if you can find a better one. Package Maker will let you edit settings which it then completely ignores. The Help for it is also really bad. Iceberg was suggested to me, but I haven't gotten the hang of it yet. My package does basically what you are asking for. * Introduction - > click "Continue" * License Agreement * Destination Select -> This is disabled, all they can do is pick "Continue" * Installation type -> Only standard installation is allowed. Click "Install" Program installs and presents summary, followed by another click to close the window. I would consider using a standard, simple package install. Why would you want your Mac OS program to not install like a Mac OS program?

1 0