site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com 2. Have the user run "SetFile -a B" -- Is the SetFile command included on all 10.3+ machines? -- -- I could add the SetFile in the postflight script probably. -pmb _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... At 9:46 AM -0700 5/5/06, Raymond Walsh wrote: I am installing an iTunes plug-in (a ".bundle" file) using Iceberg 1.1.6 to generate the pkg. Users are reporting very frequently that the double-clicking on the bundle file "opens like a folder." So I suspect the OS is not registering it as a bundle. -- When iTunes fails to load the plugin, I have them locate the bundle file and dub-click it to test whether it is a bundle or a folder. Once the user manages to make the OS "bundle-ify" the file, iTunes will load the plugin. I have seen two on-topic suggestions for this: 1. Be sure the PkgInfo is inside the bundle. I am sure it is inside the bundle's contents folder. --x.bundle/ \--Contents/ \-- Info.plist \-- PkgInfo \-- Resources/ \-- MacOS/ Is there some other way to make sure that the Bundle Bit is set when installing a ".bundle" ? Well, the bundle bit is not necessary for the OS to treat a folder as a bundle. It's just one of many ways the OS will decide the folder is a bundle. Unfortunately, I don't know why your bundle isn't being recognized as one. If setting the bundle bit is the only way your bundle gets detected, then something is incorrect about your bundle structure, because the bit should not be necessary. This email sent to site_archiver@lists.apple.com