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

Bug #1870 pear makerpm dependancies
Submitted: 2004-07-14 11:32 UTC
From: wtatam at premierit dot com Assigned: cellog
Status: Closed Package: PEAR
PHP Version: 4.3.7 OS: Linux
Roadmaps: (Not assigned)    

 [2004-07-14 11:32 UTC] wtatam at premierit dot com
Description: ------------ pear makerpm package.tar.gz does nto create any Require statments in the spec file and so the rpms will install but then your scripts will fail with messages like "Failed opening required 'XML/Util.php'" even though the relevent package.xml files contain blocks like <deps> <dep type="pkg" rel="ge" version="0.4.2" optional="no">XML_Util</dep> <dep type="pkg" rel="ge" version="1.1.0" optional="no">XML_Parser</dep> <dep type="pkg" rel="has" optional="no">PEAR</dep> </deps>


 [2004-10-22 06:09 UTC] cellog
There's no reliable way to handle this - how do you know what the names of the other .rpms will be? If you have any bright ideas, a patch would be most helpful.
 [2004-10-22 09:09 UTC] wtatam at premierit dot com
We know exactly what the other rpms are called as all rpms build of pear modules are called PEAR::$module_name so the spec file simply need to have "Requires: PEAR::$module_name >= $version"
 [2004-10-22 14:46 UTC] cellog
OK. I am not at all familiar with the internals of rpm. Could you provide an example of what a requires statement looks like and if it exists, an optional dependency? Also, where do these go in the spec? Gre
 [2005-02-01 10:56 UTC] wtatam at premierit dot com
All that is required is a spec file with the following lines within the header Requires: PEAR::$dependant_module_name >= $version Requires: PEAR::$some_otherdependant_module_name >= $version Given this script builds all the pear rpms we know the exact name of what the rpm on which this one is dependant is called. e.g XML::Parser becomes PEAR::XML_Parser
 [2005-04-03 05:18 UTC] cellog
This bug has been fixed in CVS. In case this was a documentation problem, the fix will show up at the end of next Sunday (CET) on In case this was a website problem, the change will show up on the website in short time. Thank you for the report, and for helping us make PEAR better. this also highlighted problems with installroot in PEAR 1.4 Note that this fix will not be backported to 1.3.x
 [2005-11-21 15:36 UTC] bugs at timj dot co dot uk
A patch which applies against older PEAR versions is at See also and for some discussion of generating RPM deps for declared dependency types other than "package" (e.g. "ext").