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

Re: Explaining why install failed.
by Xochitl Lunde 11 Mar '10

11 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 > On Mar 11, 2010, at 1:28 PM, Xochitl Lunde wrote: > > I have a preflight script now which checks if more than one user is > logged in and will fail if additional users are logged in. I am > using Iceberg to create my package, and my script is just a basic > shell script. How can I get a message back to the installer that > says something about why the install failed? > > No. As a matter of fact, failing during a preflight is NOT > SUPPORTED. Please do your testing in InstallationCheck/VolumeCheck. > I'm not using PackageMaker anymore because I wasn't able to get any help with it before everyone said to use Iceberg. I see that PackageMaker has an option for Package requirements "Logged-in Users". I don't see this option in Iceberg. Is it possible to script the check into the preinstall and be able to get a meaningful response back to the user if there is a failure? I can't figure out how to get a message to the user if any of my install scripts fail. I don't get a good message in my Console.app logs either. It tells me what script failed, but none of the messages in my script make it through. Since you've been so kind to answer me, I have another question as well. When I was using packagemaker, I was trying to create a check for 64-bit systems. However, the check I created always failed on my 64-bit systems. I used the "64-bit Instructions Available" choice, but apparently none of my 64-bit machines can pass the check. Is this check buggy? What hardware would actually pass the check? Thanks!

1 0

Re: Explaining why install failed.
by Bill Coderre 11 Mar '10

11 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

Explaining why install failed.
by Xochitl Lunde 11 Mar '10

11 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: Sub-packages for metapackage and "No payload could be found" warning
by Xochitl Lunde 11 Mar '10

11 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 <installer-dev-bounces+xochitl_lunde=tripplite.com(a)lists.apple.com> wrote on 03/11/2010 10:23:51 AM: > I am trying to create a metapackage with PackageMaker 3.0.4/179. I have > dragged and dropped several packages into "Contents" area, and each one has > its own choice associated (so that I can set up Requirements). I need a > metapackage because it's the friendliest option for both end user (i.e. > personal computers) and managed computer (i.e. organizational computers) > installs. > > The first sub-package imported is one I've built, and it works fine. It > shows an actual package icon in the Contents list, and PackageMaker > continuously prompts me to use its install resource for the installation. > > The second and third sub-packages are individual packages provided by a > third party, so I have no real control over them. They are each for the same > non-Universal application -- so they are individual installers for Intel and > PowerPC editions of the same application version. (The packages are both > named the same.) When these are imported into PackageMaker, they show up as > folders and do not nag me about using the installer resources. No > information -- such as title, version, etc. -- is imported from the > packages. > > When building, PackageMaker provides the same warning about the second and > third sub-packages: > > "No payload could be found. The package will not be built." > > Building the metapackage results in a bundle that contains a "Packages" > subdirectory with only the first package (the one I built). > > The .pmdoc file is set up for a minimum target of Mac OS X 10.5 and the > metapackage is listed as a distribution. The second and third packages' > Requirements are set to try to enable their Choice only when the correct > architecture is encountered. > > Without seeing or knowing more about the second and third package, can > anyone provide any guidance as to why they act so differently and don't > build into the metapackage? > > Thanks! > > > -- > Jeremy Have you tried building your new package using Iceberg instead? Maybe you will get some better error messages out of it, even if you discover you can't exactly do what you want. I really struggled with Package Maker in the last couple of months, and I spent a lot of time figuring out that it wasn't saving certain settings between runs. I have noticed that when I use package maker, it seems to make a binary file that I can't click "Show Contents" on like I can with most packages. Finder seems to treat most of the third party packages that I have as directories, whereas the items made by packagemaker are being treated like single files. I wonder if PackageMaker is then treating your other packages as folders and not as packages at all? I am not very impressed with Package Maker, and I wouldn't be surprised if someone told me it doesn't work great with other packages that were not created using Package Maker. There are special rules about what kinds of packages can go in other packages also. I'm not very familiar with them, but I remember seeing that somewhere. It might be in the Mac OS X Software Delivery Guide.

1 0

Sub-packages for metapackage and "No payload could be found" warning
by Jeremy Reichman 11 Mar '10

11 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:subject:from:to:message-id:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=dsUqFP+WJtZs3bmYbfYdzwZZWpE=; b=gbMaiBfUr5dRt1eEDKLqGtM0p5LokQju8AfST18BBEdHBPJpEupzLKV1TJBJtyhuHmja1afl/sbXFYt16wl2LDPN0tJBhbBYTPOyazd21UfXxRfLyeEBbuCCbxhDnIwoRm2fRDslUirXRik5Aq242sMGpEzrEMjdVInYCW1LCRU= Thread-index: AcrBNzwmo7QjJulaAE+LMT+fI2BQ7A== Thread-topic: Sub-packages for metapackage and "No payload could be found" warning User-agent: Microsoft-Entourage/13.3.0.091002 I am trying to create a metapackage with PackageMaker 3.0.4/179. I have dragged and dropped several packages into "Contents" area, and each one has its own choice associated (so that I can set up Requirements). I need a metapackage because it's the friendliest option for both end user (i.e. personal computers) and managed computer (i.e. organizational computers) installs. The first sub-package imported is one I've built, and it works fine. It shows an actual package icon in the Contents list, and PackageMaker continuously prompts me to use its install resource for the installation. The second and third sub-packages are individual packages provided by a third party, so I have no real control over them. They are each for the same non-Universal application -- so they are individual installers for Intel and PowerPC editions of the same application version. (The packages are both named the same.) When these are imported into PackageMaker, they show up as folders and do not nag me about using the installer resources. No information -- such as title, version, etc. -- is imported from the packages. When building, PackageMaker provides the same warning about the second and third sub-packages: "No payload could be found. The package will not be built." Building the metapackage results in a bundle that contains a "Packages" subdirectory with only the first package (the one I built). The .pmdoc file is set up for a minimum target of Mac OS X 10.5 and the metapackage is listed as a distribution. The second and third packages' Requirements are set to try to enable their Choice only when the correct architecture is encountered. Without seeing or knowing more about the second and third package, can anyone provide any guidance as to why they act so differently and don't build into the metapackage? Thanks! -- Jeremy _______________________________________________ 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

Build metapackages from the command line with PackageMaker 3
by Jeremy Reichman 10 Mar '10

10 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:subject:from:to:message-id:mime-version:content-type:content-transfer-encoding; s=smtpout; bh=KLK3Ah3SVnPP+LWyvA2zPvpk1lI=; b=O5xfsAMhkqaOgdRIPsPD9/+/zUWhw31RVNEkljyUH8J2+CMnea1NBqk1CoYcL0d0ivuptX4negwqyBaYNHKMEx5YhdiCe8+p7EnpPUBHoaIL2RiIxF+jvmPjfEVUKIjeHW7R/pu0yyJtmfd6dqd0l16v54oU5O3LhE8OMDD4mU0= Thread-index: AcrAZsZSPNHF7aO0GkSrBRbWh+uTXw== Thread-topic: Build metapackages from the command line with PackageMaker 3 User-agent: Microsoft-Entourage/13.3.0.091002 I've come across other posts about this in the archives and on the 'net, but have not found a solution, so I'm going to ask again. Has anyone been able to use the backwards-compatible mode of PackageMaker 3's command line tool to build a metapackage installer? If so, I'd like to know the magic to make it work without having created a .pmdoc first. When I try to build such and installer, I get this: $ PACKAGE_TITLE="Insert metapackage title here" $ /Developer/usr/bin/packagemaker -build -ms "./packages" \ -p "./build/$PACKAGE_TITLE.mpkg" \ -i "./Info.plist" \ -v Building in backwards compatible mode ERROR: No packages to build. [Fwiw, I've filed this as <rdar://problem/7728789>, because it happens with every metapackage I try to build with any selection of pre-existing sub-packages.] I'm trying to use the backwards compatible mode of /Developer/usr/bin/packagemaker so that I don't have to generate a .pmdoc file with the GUI PackageMaker first. It appears that PackageMaker 3's new command line options would allow building metapackages if a .pmdoc was present, but I can't see a way to use those new options without having a .pmdoc first. Thanks! -- Jeremy _______________________________________________ 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: IFPkgFlagInstalledSize giving different results on Leopard andSnow Leopard
by ajay bhardwaj 10 Mar '10

10 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:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=UYw3XrfXk3trQcAY7PQyhXvU0luS75bwWE8yv9Rsc74=; b=cYgASvQ3vYzTMSp8BhjDWcfYwG/bMlJGEOpCUVBczMG+0oAxT2KtTGqWT/uLjP9hYl rKyIoUeLzmBZWhJXdaJrfVvkT92j8FZ2A/tXq2ScJK6TI14YhclAi2KNb/rTHD8nMJFP cJylO41GY/cU014Sh4n+ZxKgW9IGD1qgeQSFA= 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; b=Pj0BXCiGezu/HgNzUyG5nDxUUZH5OM32CB0MrKBZi8SjBhbqbtOMNHhOPEh4odI6zj m+DIVoAEhib9DF0n8CvEMF9XZb9n7NEX0wJM+BAz9Upl3XItVC956SP08eP+n3SrRkXZ kkXD1dFufzG9DfQixlyw/yrZCd48enD37ZKPI= _______________________________________________ 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: IFPkgFlagInstalledSize giving different results on Leopard andSnow Leopard
by Paul Sanders 09 Mar '10

09 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

Fwd: IFPkgFlagInstalledSize giving different results on Leopard and Snow Leopard
by ajay bhardwaj 09 Mar '10

09 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:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=yATt9nqQSun7BEpusAeFX2TgIjfsoojCavMu9GfX2jc=; b=pQ3viohVQWY9jKGPZpq2UoUKh0KCQHC9khro/ZO18KtdXxafzxyZLxRU15H8Rv0N3N bAmWttJw/GfC3vdUPa6fVhZvhHjSUlyaYFOloTqdlfCKyiJpi2FpibEaxZakrtq82SWf 6WGbSvZf8C72KYfKTI0RHP//JxvxInldyjTTI= 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; b=V3wJzj4fwBPuyOnuwRVezT9JwrwCdQUyX/6h6vWkYVhDK9/MG8/OMO2KYbTj/ttnCx CHCo9M60WmgW2SyDPiv73dk1LSbipOy3axH/K6hQCq3Dw+a3NHrvVUO104c25IDZaMIo OW6l01N2whLYnnABVGiQD1dfcQrHxBJI1pj4o= _______________________________________________ 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 not building if Scripts folder contains any frameworks
by Sravana Kumar 09 Mar '10

09 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:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=faJ5z3q0QdCbrdmp7E+rP7ooSEkQwDt8nebDh76U8K4=; b=pdclG9bie0y8jtmmZOvCpvzFgJBwizACBnrGnP17tp8tsOBfgYy/GgQmv0BHnofvDp PXfJLcZ2XGXNIiGtTbgXFvEPa9Iw8citVnGzEWBvuXKOpeW8v/1zy9ggdwUXPB3rsTJZ uZZsAoob6RSFDPFYu9Xpes/F09e/sR1bVvQuA= 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; b=Yt4z9MKBt/hX+7RaWDuf1MVclHj3+MKdsQ6b6wwRZYztBk1P2MEP2w2TqfsY81BiqF OsuET37IhWaafGmICgBh/IMSQ7C1boiS9NWpDelDTpDB+BA69Yxx/nSUZdYmmjZmlVaH fi1aDQCK/NRtUsCVXzq6dv11AbwjrF3N4ZqFU= _______________________________________________ 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