Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.15

Bug #7842 package-dependencies wrong type display with package 1.0
Submitted: 2006-06-08 22:19 UTC
From: farell Assigned: pajoye
Status: Closed Package: PEAR (version 1.4.9)
PHP Version: 4.4.2 OS: windows xp
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 : 28 - 4 = ?

 
 [2006-06-08 22:19 UTC] farell (Laurent Laville)
Description: ------------ while running command pear package-dependencies path_to_file_package_1.0_xml with a package that has an extension as dependency, i've noticed that column "Type" has 'Ext' where it should have 'Extension'. This bug come from PEAR\Command\Common.php, property $_deps_type_trans (line 77) Remember into package xml 1.0 types are pkg for package ext for extension and so on ... Replace line 77 'extension' => 'extension', By 'ext' => 'extension', Laurent Test script: --------------- pear -c pear.ini package-dependencies D:\php\pear\PHP_CompatInfo\package.xml Expected result: ---------------- DEPENDENCIES FOR PEAR/PHP_COMPATINFO ==================================== REQUIRED? TYPE NAME RELATION VERSION Yes PHP >= 4.3.0 Yes Extension tokenizer == No Package Console_Table >= 1.0.1 No Package Console_Getopt >= 1.2 Actual result: -------------- DEPENDENCIES FOR PEAR/PHP_COMPATINFO ==================================== REQUIRED? TYPE NAME RELATION VERSION Yes PHP >= 4.3.0 Yes ext tokenizer == No Package Console_Table >= 1.0.1 No Package Console_Getopt >= 1.2

Comments

 [2006-06-08 22:27 UTC] pajoye (Pierre-Alain Joye)
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.