Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.15
Bug #5999 support for baseinstalldir broken in package2.xml format
Submitted: 2005-11-17 14:05 UTC
From: demianturner Assigned: cellog
Status: Closed Package: PEAR
PHP Version: 4.3.11 OS: fedora core 4
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 19 + 1 = ?

 
 [2005-11-17 14:05 UTC] demianturner
Description: ------------ Adding 'installexceptions' generates the same XML output as package.xml, but with package2.xml the baseinstalldir directive appears to be ignored. <file baseinstalldir="HTML" md5sum="a32ea0d5899960d640815ace42a876b3" name="Tree.php" role="php" /> <file baseinstalldir="Seagull" md5sum="f1d0aecdf57b18ad8b9fb695e9c45a82" name="VERSION.txt" role="data" /> When installing a package described in package.xml format the 'baseinstalldir' directives work as expected, but for package2.xml they are ignored and all files are installed in 'Seagull' and not 'DB' as specified.

Comments

 [2005-11-17 14:08 UTC] demianturner
and not 'HTML' as specified ..
 [2005-11-27 03:02 UTC] cellog
can you verify that baseinstalldir="HTML" is in package2.xml? I created a test case that works as documented, so I wonder if this is indeed a PEAR_PFM bug
 [2005-12-01 07:45 UTC] cellog
verified. This is a serious bug. When the installer tries to "flatten" the file list, it removes all custom baseinstalldir attributes. I will be releasing PEAR 1.4.6 with this fix very quickly.
 [2005-12-01 07:52 UTC] cellog
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.