From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ncurses-libs: provide libncurses.so.5
Date: Mon, 27 Jul 2020 03:44:12 +0200 [thread overview]
Message-ID: <20200727014412.ZVTeDte385s7yawEa3PNmYct0e4KC5aL5V4QNOko9jM@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: 974 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/23862#issuecomment-664075895
Comment:
ncurses5 and ncurses6 are not ABI compatible, you can configure ncurses6 to use ABI version 5, but not both at once (the build will create `.so.5` or `.so.6` libs depending on the ABI you set)
@ahesford opensuse and debian as well as others probably provide both 5 and 6, but they're separate builds, e.g. like we do widechar and non-widechar builds right now, we'd also need to add two more builds for the ABI version 5
either way, a symlink won't cut it and this PR was rightfully closed
I don't think there's a need to have builds for 5, we don't have any responsibility to cater to third party proprietary binaries we don't package, if you want ncurses5 obtain it through other means, if it works with the symlinks then keep your own symlinks but that's only by chance that it works and they definitely shouldn't be packaged
next prev parent reply other threads:[~2020-07-27 1:44 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 ` [PR PATCH] [Closed]: " ahesford
2020-07-27 1:42 ` q66
2020-07-27 1:44 ` q66 [this message]
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=20200727014412.ZVTeDte385s7yawEa3PNmYct0e4KC5aL5V4QNOko9jM@z \
--to=q66@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).