Bug 397051
Summary: | Why built with --disable-static | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Reindl Harald <spam2> |
Component: | GeoIP | Assignee: | Michael Fleming <mfleming+rpm> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | ||
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: | 2007-12-05 11:47:31 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
Reindl Harald
2007-11-23 16:32:16 UTC
I would consider an inability to build against a dynamic library a bug in the upstream software - have you asked the Webalizer Xtended author why this is? (as an old Webalizer user I'm kind of happy someone still cares about it!) The Fedora packaging guidelines prohibit this in most cases (see http://fedoraproject.org/wiki/Packaging/Guidelines#head-2302ec1e1f44202c9cc4bcce24cb711266557ad7) and I happen to agree with them on these points. Ulrich Drepper (RH and glibc hacker) outlines it better here: http://people.redhat.com/drepper/no_static_linking.html. Point 1 is of great interest to both of us as packagers, point 2 is also especially important if you're a sysadmin/security person (like me ;-)) In short, I'm not willing at this point to ship a static libGeoIP.a. I - and I will wager other potential users of your proposed package - would really like to see this fixed *correctly* upstream rather than inelegant hacks in our respective packages. While simple to do for me (just a few lines in the spec) I'd be encouraging bad practice as well as lumping all manner of suffering on anyone using it (yes, you'd have to recompile your package on every single bugfix/security release vs. only recompiling if the SONAME changes in cases of a dynamic library) Sorry for the bad news. |