Bug 190252
| Summary: | /usr/lib/php/pear used for "noarch" pear RPM. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Remi Collet <fedora> |
| Component: | php-pear | Assignee: | Joe Orton <jorton> |
| Status: | CLOSED ERRATA | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | gauret, j, rpm |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 1.4.9-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-05-17 08:14:15 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 190066, 190101, 190156 | ||
You should have this bug block your two package submissions. I agree that on reflection %{_libdir} was a poor choice. Shame we don't have a
%{_libdirnoarch} or something.
I would suggest putting the XML files somewhere within /usr/share/pear to avoid
creating another namespace. Maybe /usr/share/pear/pkg-xml or similar? I just had
a look to see how PLD do it but they don't seem to bother registering PEAR
modules with the PEAR package database AFAICT (I picked a random couple of specs
from http://cvs.pld.org.pl/SPECS/ )
FYI, Mandriva uses %{_datadir}/pear/packages/%{_pearname}.xml
See
http://cvs.mandriva.com/cgi-bin/cvsweb.cgi/SPECS/php-pear-Date/php-pear-Date.spec?rev=1.2
for example, the other pear packages look the same.
%{_datadir}/pear/something was my first idea, but we have to think that
%{_datadir}/pear is in the include_path of php. So using a directory under this
will make the .XML visible from php scripts (probably not a problem).
OK, let's at least use a .directory in /usr/share/pear, since PEAR is using that for private stuff already... so... /usr/share/pear/.rpmxml, /usr/share/pear/.pkgxml, any preferences? No preference. /usr/share/pear/.rpmxml seems a good choice. I'd tend to go for %{_datadir}/pear/.pkgxml (since it's not really anything to
do with RPMs; the content of the directory is just pure PEAR package XML stuff)
but either would be OK.
So, ok for %{_datadir}/pear/.pkgxml
I'll prepare the spec for my RPM with this.
%{_datadir}/pear/.pkgxml is owned in php-pear-1.4.9-1, on its way to
updates-testing -- please test it out.
php-pear-1.4.9-1 works fine for me. |
Description of problem: PHP own the %{_libdir}/php/pear which is used to store the XML files of the pear extensions packages (actualy on DB in the extras, but more will follow). This extension are noarch, so they probably shouldn't use %{_libdir} Version-Release number of selected component (if applicable): php-5.1.2-5 Actual results: On x86_64, php own /usr/lib64/php/pear while php-pear-DB use /usr/lib/php/pear. A solution is probably to use a directory under %{_datadir}, for example /usr/share/pear-packages which could then be owned by php-pear. You could also read the Extras Review Request for php-pear-Mail in Bug #190066 I think i have to wait for this bug before to submit my other RPM. Thanks.