Bug 801922
Summary: | liblfc.so can be used as a runtime module | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Brian Bockelman <bbockelm> |
Component: | lcgdm | Assignee: | Mattias Ellert <mattias.ellert> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | el5 | CC: | mattias.ellert, steve.traylen |
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: | 2012-03-10 19:44:34 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
Brian Bockelman
2012-03-09 20:52:51 UTC
Neither including the .so symlink in the library package, nor adding a runtime dependency on the devel package is the rigth thing to do in this case. The proper thing to do when packaging for Fedora and EPEL is to patch the package dlopening the library to dlopen the versioned library, i.e. liblfc.so.1 in this case. See for example the discussion in the Package Review in bug #592670 comment #17. |