Description: ------------ When a package that utilizes a baseinstalldir is split into multiple subpackages the relevant files from the original package are moved into any of the sub packages but due to the subpackage dynamic registry voodoo magic on the files was not taking baseinstalldir into an account Example: Package 1 has file A.php B.php C.php in older releases and uses baseinstalldir Package 1 gets Package 2 as a sub package and contains B.php Package 1 gets Package 3 as a sub package and contains C.php The new Package 1 now only contains A.php This is all done to keep BC and thus package 2 and 3 get the same baseinstalldir as Package 1 Upgrading would cause the installer to install B.php and C.php but when the upgrade of Package 1 kicks in it will think B.php and C.php are gone and deletes it from the file system. Real world scenario reduced: PEAR_PackageFileManager was causing files installed by PEAR_PackageFileManager2 and PEAR_PackageFileManager_Plugins to get removed in the installation process. Test script: --------------- Expected result: ---------------- Actual result: --------------

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.