From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Modify ncurses package to provide libtinfo
Date: Mon, 06 Dec 2021 21:06:23 +0100 [thread overview]
Message-ID: <20211206200623.YygW3PR5byDT4iy4jnTTfaaJYU3Y862gx7yDnoIDWjk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11718@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
Closed issue by lambdadog on void-packages repository
https://github.com/void-linux/void-packages/issues/11718
Description:
This has mostly caused issues in regards to Haskell for me personally, as mentioned in #7403 (although I've also had issues with building several Haskell packages, including Haskeline), but I can only imagine there are issues elsewhere as well.
While it's possible to modify software packaged for Void to use libncurses rather than libtinfo, I assume, when used for a developer system it's often impossible or infeasible to modify all of the software and libraries you're using to conform to Void Linux's choices.
As mentioned in [this comment](https://github.com/commercialhaskell/stack/issues/4711#issuecomment-480614106), most distributions have standardized on providing libtinfo along with libncurses, and I'm of the opinion that Void Linux should follow suit.
next prev parent reply other threads:[~2021-12-06 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11718@inbox.vuxu.org>
2020-01-31 0:56 ` voidlinux-github
2021-12-06 19:14 ` hasufell
2021-12-06 20:06 ` q66 [this message]
2023-10-14 23:59 ` bm16ton
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=20211206200623.YygW3PR5byDT4iy4jnTTfaaJYU3Y862gx7yDnoIDWjk@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).