Bug 173806
Summary: | php-pear package does not have Provides for the packages it includes | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tim Jackson <rpm> |
Component: | php | Assignee: | Joe Orton <jorton> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | joshkel |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-12-01 22:23:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tim Jackson
2005-11-21 14:32:51 UTC
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. |