Bug 499837
Summary: | readline not properly linked against ncurses | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Gordan Bobic <gordan> |
Component: | readline | Assignee: | Miroslav Lichvar <mlichvar> |
Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE <qe-baseos-auto> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | bjoern, eerott, gdeschner, pasteur |
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: | 2009-05-08 15:28:00 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
Gordan Bobic
2009-05-08 14:18:46 UTC
The problem is it can be linked with libtermcap or libncurses, they both provide similar API. Forcing libreadline to be linked with libncurses would possibly break applications linked with libtermcap. It's up to application to choose which library should be used, usually it's handled in configure scripts. In RHEL6 only terminfo will be supported, so readline is linked with libtinfo from ncurses package. (In reply to comment #1) > The problem is it can be linked with libtermcap or libncurses, they both > provide similar API. Forcing libreadline to be linked with libncurses would > possibly break applications linked with libtermcap. Debian solved this problem already in the last century (archives went only to back 1997, so I don't know exactly when). As libncurses provides the libtermcap API, in Debian /usr/lib/libtermcap.so is just a symlink to /usr/lib/libncurses.so. So things built against both libtermcap and libncurses work just fine. Therefore this is only a problem for binary-only programs. But readline is GPL, so it cannot be used in binary-only programs and therefore those cannot (legally) have this issue. For binary-only programs that linked just libtermcap and needed its ABI, Debian had libtermcap-compat package which provided the (inferior) /etc/termcap terminal description database and ABI compatible /usr/lib/libtermcap.so.2 library. This package seems to have been dropped in Debian Etch (released 2007), so I guess all of these obsolete binary-only programs had been fixed by then. FYI: We just got a complaint from a user that our program doesn't work on RHEL5 (well, actually CentOS). Forcing our program to directly link something from which it depends only indirectly is clearly broken[1], so I don't think we're going to do that. Couldn't you just fix this brokenness? [1] Distros complain about that (I think Fedora included) and it would also cause the issue which you claim to be the reason why don't fix this bug! |