From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ncurses-libs: provide libncurses.so.5
Date: Mon, 27 Jul 2020 03:25:04 +0200 [thread overview]
Message-ID: <20200727012504.fGtK7u9X8ryEtfxLiNWGyJiRS4WyI2W4OKvnZm3m5sU@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: 964 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/23862#issuecomment-664072165
Comment:
The symlink you request is not a robust solution to the problem of a missing `libncurses.so.5`. Source versions 5 and 6 of `libncurses` both allow the shared object to be built with ABI version 5 or 6, which leads to confusion and potential incompatibilities. Your version of `megacli` was probably built on a distribution that builds `ncurses5` v5 with the v6 ABI, so things just happen to work when you make the symlink on Void. One of the responses to the Reddit post you linked makes this point.
It looks like [openSUSE uses the v5 ABI](https://software.opensuse.org/package/libncurses5).
The confusing versioning schemes are the reason the Void package recently dropped all v5 symlinks; there is nothing left in the official repo that relies on them. You are welcome to create your own symlink to fix `megacli`.
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 [this message]
2020-07-27 1:25 ` [PR PATCH] [Closed]: " ahesford
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=20200727012504.fGtK7u9X8ryEtfxLiNWGyJiRS4WyI2W4OKvnZm3m5sU@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).