Hide Forgot
Description of problem: The php-pear package does not have Provides: for the bundled packages (including DB, HTML_Template_IT, XML_RPC, XML_Parser etc.) It also does not have a Provides: for the core package itself (i.e. PEAR, which is in itself a PEAR package), other than the php-pear package name which is versioned according to the PHP version rather than the actual PEAR version. Based on the convention adopted by default when using "pear makerpm" (that is, PEAR::Package_Name), the php-pear package should include the following Provides: PEAR::XML_RPC = 1.4.0 PEAR::XML_Parser = 1.2.6 PEAR::PEAR = 1.3.5 etc. Version-Release number of selected component (if applicable): php-pear-5.0.4-10.5 How reproducible: Always Steps to Reproduce: 1. rpm -q --provides php-pear Actual results: php-pear = 5.0.4-10.5 Expected results: php-pear = 5.0.4-10.5 PEAR::PEAR = 1.3.5 PEAR::XML_RPC = 1.4.0 PEAR::XML_Parser = 1.2.6 etc.
There is of course the related issue of whether PEAR::Package_Name is a good naming convention in accordance with FC packaging generall. Other obvious alternatives include: - php-Package_Name (this emulates the CPAN/pear-Foo_Bar convention) - php-pear-Package_name Personally I would choose php-Package_Name to make PHP/PEAR match Perl/CPAN. Either way, it's worth bearing in mind that the choice may impact on the patch in on bug #173814, and indeed may require a FC-specific patch to newer PEAR versions to match the chosen convention, when newer upstream versions that include RPM dep generation are pulled in.
I'm going with this style: Provides: php-pear(Archive_Tar) = 1.3.1 Provides: php-pear(Console_Getopt) = 1.2
Done in php-pear-1.4.5-2. If anyone has strong objections to this syntax please pipe up.