Hi everyone
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/
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.
Is there some other way to make sure that the Bundle Bit is set
when installing a ".bundle" ?
(Sorry for this off topic question) Does anyone know why SetFile
would have given a -5000 to an Admin user?
Thank you for any suggestions
Sincerely
Raymond Walsh