If you have a metapackage in 10.1 format and at least one of its package in 10.2 and 10.1 format, Installer won't be able to run the Installation.
|Suggestion:||Have all your packages and metapackages be in 10.1 AND 10.2 format.|
Because of a bug in Installer when you install a package containing Universal Binaries that you've previously installed, the installation process will crash.
|Workaround:||Remove the package receipt in the postflight script when installation is performed on Mac OS X < 10.3.|
If you have a metapackage which embeds a relocatable package, the location selected by the user in Installer won't be taken into account.
|Suggestion:||None. It's a bug in Installer.|
It's not recommended to ask for Admin authorization in Mac OS X 10.3 with a relocatable package. There's a bug which can result in incorrect permissions on some components of the default location.
|Suggestion:||None, it's a bug in Installer. Just avoid relocatable package and Admin Authorization (ask for root authorization instead) if you can.|
If you want to disable some packages within a metapackage, it's not recommended to use a VolumeCheck script as there's a bug in Installer on Mac OS X 10.3.9 (and maybe some earlier versions). The consequence is that the results are not correct sometimes.
|Suggestion:||Use InstallationCheck scripts if you can.|
Due to a bug in Installer or in the Installation.framework, some requirements are not properly processed because of a missing bytes swap.
|Suggestion:||None, you can only pray that nobody is running the first releases of Mac OS X 10.4 Intel.|
Due to a bug in Installer, 'bundle' requirements may lead to a crash of the installation with some applications bundle. If you're just checking for the presence of a bundle, it's working OK.
|Suggestion:||Check your installer before shipping.|