From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: ncurses-libs: provide libncurses.so.5
Date: Mon, 27 Jul 2020 03:25:07 +0200 [thread overview]
Message-ID: <20200727012507.V9RaBzduo4mRJMHSy5o9PeMgU8Iu2AqiHHrLYBPXFG4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23862@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
There's a closed pull request on the void-packages repository
ncurses-libs: provide libncurses.so.5
https://github.com/void-linux/void-packages/pull/23862
Description:
@q66 can you please allow this symlink at least?
I state my case:
a. I need /usr/lib/libncurses.so.5 to run a binary (fwiw, megacli to manage a LSI raid controller -- unfortunately there's no other way to manage the raid arrays without rebooting to bios)
b. This binary runs without any problem with the symlink
c. I think this is expected since the ncurses 6 library is both API and ABI compatible with ncurses 5, according to its own documentation:
> This release is designed to be source-compatible with ncurses 5.0 through 6.1; providing extensions to the application binary interface (ABI). Although the source can still be configured to support the ncurses 5 ABI, the reason for the release is to reflect improvements to the ncurses 6 ABI and the supporting utility programs.
d. Someone else requested it on reddit (https://www.reddit.com/r/voidlinux/comments/hprhjp/where_to_download_libncursesso5/)
I'm not sure about all the other symlinks that https://github.com/void-linux/void-packages/commit/854828d619792969aef4315747c768a618434acd removed, an alternative would be to revert that one and apply https://github.com/void-linux/void-packages/pull/23660/commits/37f47318107975b56192a84fec9502b534628f4d from PR #23660 instead.
next prev parent reply other threads:[~2020-07-27 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 0:54 [PR PATCH] " gt7-void
2020-07-27 1:25 ` ahesford
2020-07-27 1:25 ` ahesford [this message]
2020-07-27 1:42 ` q66
2020-07-27 1:44 ` q66
2020-07-27 1:48 ` q66
2020-07-27 2:01 ` gt7-void
2020-07-27 2:08 ` q66
2020-07-27 2:10 ` q66
2020-07-27 2:43 ` gt7-void
2020-07-27 2:51 ` ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200727012507.V9RaBzduo4mRJMHSy5o9PeMgU8Iu2AqiHHrLYBPXFG4@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).