November 2004 - Installer-dev

Re: PackageMaker command line/meta pkg/Panther
by Stéphane Sudre 09 Nov '04

09 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On lundi, novembre 8, 2004, at 11:27 PM, John Rosasco wrote: This is because it was just to give an idea ;) To go into details, a metapackage once built looks like this: MyMetapackage.mpkg -+- Contents -+- PkgInfo | +- Info.plist | +- Resources -+- Description.plist | +- [MyMetapackage.info] | +- [MyMetapackage.list] | + ... build -+- .containedPkgs -+- Your Packages | +- MyMetapackage.mpkg Now, if you want the solution involving a 3rd party tool: Hope it helps. -- 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.… mkdir $HOME/build/ cp -R Meta/*.pkg $HOME/build/ mkdir $HOME/build/MyMetapackage.mpkg mkdir $HOME/build/MyMetapackage/Contents cp Info.plist $HOME/build/MyMetapackage/Contents/ ##echo pmkrpkg1 > $HOME/build/MyMetapackage/Contents/PkgInfo ## As this puts a 0, you need to copy a file instead cp -R resources $HOME/build/MyMetapackage/Contents/Resources cp Description.plist $HOME/build/MyMetapackage/Contents/Resources/ How is it that this can hide the packages ? Right now, given my Info.plist file as described above, it doesn't appear possible that these steps could produce a meta-package that would work with my Info.plist file or hide the packages. Items in [] are optional and used for Mac OS X < 10.1 compatibility ... represents .lproj folders, scripts, and additional resources (background picture), etc... So if you already have the Info.plist and the Description.plist file and you don't care about 10.1 compatibility (which you wouldn't get anyway using PackageMaker from the UI last time I checked), what you just have to do is build the file hierarchy yourself. Since you want to put the Packages in a .containedPkgs folder, your hierarchy would look like this ("build" is a temporary folder I think it's wise to create): As I'm not a king of shell scripts (but I think it can be done just via a shell script): 1) Create the build folder 2) Create the .containedPkgs within the build folder 3) Copy your Packages in the .containedPkgs folder 4) Create the MyMetapackage.mpkg folder 5) Create the Contents folder within the MyMetapackage.mpkg folder 6) Copy a PkgInfo file from a Metapackage you built manually in the Contents folder 7) Copy the Info.plist in the Contents folder 8) Copy the Resources folder in the Contents folder 9) Copy the Description.plist file in the Resources folder 1) Download Iceberg on VersionTracker 2) Create a new Metapackage project 3) Add your documents, settings and all (if you have a .pmsm file, you can import it to avoid steps 2 and 3). 4) Drag and Drop your built packages in the Components section 5) Save 6) Call from the command line: freeze /the_path/to/your/Iceberg/Project.packproj But I still think the shell solution is easier in your case if you don't care about 10.1 compatibility. This email sent to site_archiver(a)lists.apple.com

1 0

Can't install package.
by Pavel Golovko 09 Nov '04

09 Nov '04

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Thread-index: AcTGchy7aR/XGQmtQVGJFpXnB4H2PA== Thread-topic: Can't install package. Hello everybody! I try to install my installation package on two computers (both under MAC OS X 10.2.8). On the one computer this complete successfully, but on the other i have the following problem: First time I have to select a partition for installing, I can't select it.My partition is disabled. If I go one step back and then forward to the same step, then I can select the partition. What is the problem? This is a part of my plist file <key>IFPkgFlagAllowBackRev</key> <false/> <key>IFPkgFlagAuthorizationAction</key> <string>RootAuthorization</string> <key>IFPkgFlagDefaultLocation</key> <string>/</string> <key>IFPkgFlagInstallFat</key> <false/> <key>IFPkgFlagIsRequired</key> <true/> <key>IFPkgFlagRelocatable</key> <false/> <key>IFPkgFlagRestartAction</key> <string>RecommendedRestart</string> <key>IFPkgFlagRootVolumeOnly</key> <true/> <key>IFPkgFlagUpdateInstalledLanguages</key> <false/> <key>IFPkgFormatVersion</key> <real>0.10000000149011612</real> Thank you in advance. Regards. Pavel. _______________________________________________ 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 command line/meta pkg/Panther
by John Rosasco 08 Nov '04

08 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Stephane, thanks for the posting. Pls see response below ... On Nov 6, 2004, at 12:44 AM, Stéphane Sudre wrote: On vendredi, novembre 5, 2004, at 10:33 PM, John Rosasco wrote: Hello, <key>IFPkgFlagComponentDirectory</key> <string>../.containedPkgs</string> I currently have: Description.plist Info.plist resources Meta Can anybody tell me the answers to these two questions: It's not tested I've just typed it in Mail.app but you get the idea. My $0.02 _______________________________________________ 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'm creating a disk image from a meta package for the purposes of auto-launching installer when the disk image is downloaded from the website. I'm using the hidden packages method (with the .containedPackages directory). This is described at: http://developer.apple.com/documentation/DeveloperTools/Conceptual/ SoftwareDistribution/Concepts/sd_mpkg_anatomy.html However, this description is for PackageMaker using the UI. My Info.plist file references the .containedPackages directory as follows: In the same directory where Meta is the parent directory of .containedPackages. And, of course, the .containedPackages has all the constituent packages copied into it. (1) Is this directory structure appropriate for use of PackageMaker on the command line to create a meta package. I don't think so because when you build a Metapackage, the packages are not automatically moved/duplicated/copied to the destination. (2) Assuming the plists are correct, can anybody provide the exact PackageMaker command line to build the meta package ? I'm not sure the command line tool for PackageMaker (which is the app itself in 1.1a10 and later version) can build Metapackages. Because I just tried to make it swallow the fact that there was no root dir and the result was not that great. Anyway, assuming you have all this stuf, and you don't care at all about Mac OS X 10.1 compatibility, I don't see anything preventing you from building the Metapackage yourself: mkdir $HOME/build/ cp -R Meta/*.pkg $HOME/build/ mkdir $HOME/build/MyMetapackage.mpkg mkdir $HOME/build/MyMetapackage/Contents cp Info.plist $HOME/build/MyMetapackage/Contents/ ##echo pmkrpkg1 > $HOME/build/MyMetapackage/Contents/PkgInfo ## As this puts a 0, you need to copy a file instead cp -R resources $HOME/build/MyMetapackage/Contents/Resources cp Description.plist $HOME/build/MyMetapackage/Contents/Resources/ How is it that this can hide the packages ? Right now, given my Info.plist file as described above, it doesn't appear possible that these steps could produce a meta-package that would work with my Info.plist file or hide the packages. I have another solution which involves using a 3rd party tool which will be available this week-end but I think the solution above is the best one in this case. This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker command line/meta pkg/Panther
by Stéphane Sudre 06 Nov '04

06 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On vendredi, novembre 5, 2004, at 10:33 PM, John Rosasco wrote: Hello, <key>IFPkgFlagComponentDirectory</key> <string>../.containedPkgs</string> I currently have: Description.plist Info.plist resources Meta Can anybody tell me the answers to these two questions: It's not tested I've just typed it in Mail.app but you get the idea. My $0.02 _______________________________________________ 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'm creating a disk image from a meta package for the purposes of auto-launching installer when the disk image is downloaded from the website. I'm using the hidden packages method (with the .containedPackages directory). This is described at: http://developer.apple.com/documentation/DeveloperTools/Conceptual/ SoftwareDistribution/Concepts/sd_mpkg_anatomy.html However, this description is for PackageMaker using the UI. My Info.plist file references the .containedPackages directory as follows: In the same directory where Meta is the parent directory of .containedPackages. And, of course, the .containedPackages has all the constituent packages copied into it. (1) Is this directory structure appropriate for use of PackageMaker on the command line to create a meta package. I don't think so because when you build a Metapackage, the packages are not automatically moved/duplicated/copied to the destination. (2) Assuming the plists are correct, can anybody provide the exact PackageMaker command line to build the meta package ? I'm not sure the command line tool for PackageMaker (which is the app itself in 1.1a10 and later version) can build Metapackages. Because I just tried to make it swallow the fact that there was no root dir and the result was not that great. Anyway, assuming you have all this stuf, and you don't care at all about Mac OS X 10.1 compatibility, I don't see anything preventing you from building the Metapackage yourself: mkdir $HOME/build/ cp -R Meta/*.pkg $HOME/build/ mkdir $HOME/build/MyMetapackage.mpkg mkdir $HOME/build/MyMetapackage/Contents cp Info.plist $HOME/build/MyMetapackage/Contents/ ##echo pmkrpkg1 > $HOME/build/MyMetapackage/Contents/PkgInfo ## As this puts a 0, you need to copy a file instead cp -R resources $HOME/build/MyMetapackage/Contents/Resources cp Description.plist $HOME/build/MyMetapackage/Contents/Resources/ I have another solution which involves using a 3rd party tool which will be available this week-end but I think the solution above is the best one in this case. This email sent to site_archiver(a)lists.apple.com

1 0

PackageMaker command line/meta pkg/Panther
by John Rosasco 05 Nov '04

05 Nov '04

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hello, <key>IFPkgFlagComponentDirectory</key> <string>../.containedPkgs</string> I currently have: Description.plist Info.plist resources Meta Can anybody tell me the answers to these two questions: Thanks a million .... _______________________________________________ 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'm creating a disk image from a meta package for the purposes of auto-launching installer when the disk image is downloaded from the website. I'm using the hidden packages method (with the .containedPackages directory). This is described at: http://developer.apple.com/documentation/DeveloperTools/Conceptual/ SoftwareDistribution/Concepts/sd_mpkg_anatomy.html However, this description is for PackageMaker using the UI. My Info.plist file references the .containedPackages directory as follows: In the same directory where Meta is the parent directory of .containedPackages. And, of course, the .containedPackages has all the constituent packages copied into it. (1) Is this directory structure appropriate for use of PackageMaker on the command line to create a meta package. (2) Assuming the plists are correct, can anybody provide the exact PackageMaker command line to build the meta package ? This email sent to site_archiver(a)lists.apple.com

1 0