Description: ------------ With PFM 1.6.0a4 and PEAR 1.4.5, i've noticed that a check is missing for 'pathtopackagefile' option. You should implement the same existing test as for 'packagedirectory' option on lines 448-451. On my system, from current directory , there is no dir called 'Temp2' (i've wrote it to generate error). With the right directory ('..\..\Temp') all run fine (no notice error, of course). Test script: --------------- <?php require_once 'PEAR/PackageFileManager2.php'; $options = array( 'pathtopackagefile' => '..\..\Temp2', 'packagedirectory' => '.', 'filelistgenerator' => 'file', 'baseinstalldir' => 'HTML', 'changelogoldtonew' => false, 'simpleoutput' => true, ); $pkg = new PEAR_PackageFileManager2(); $pkg->setOptions($options); //... ?> Expected result: ---------------- No notice error message, but return a PEAR_Error if 'pathtopackagefile' directory is unknown on system. Actual result: -------------- Notice: Uninitialized string offset: -1 in [...]PEAR\PackageFileManager2.php on line 463

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.