From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: ncurses: add libtinfo.so
Date: Wed, 27 May 2020 16:29:57 +0200 [thread overview]
Message-ID: <20200527142957.ujC0dtNXhvqtLtH_FOBzypBQ_R9QLzrFEeSTPOWMc8w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21409@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
There's a merged pull request on the void-packages repository
ncurses: add libtinfo.so
https://github.com/void-linux/void-packages/pull/21409
Description:
This change add an extra library "libtinfo.so".
From the documentation:
When building the ncurses library, organize this as two parts: the
curses library (libncurses) and the low-level terminfo library
(libtinfo). This is done to accommodate applications
that use only
the latter. The terminfo library is about half
the size of the total.
This is used by some programs, which will rather look at libtinfo, than
libncurses.
Stack, the Haskell build tool, uses this to determine what resolver it needs, and I can see multiple people have had problems with Stack not running out of the box, this should fix this, and also make Stack work with the latest version resolver version (A resolver is like a set of package versions including ghc, which is supposed to work together)
prev parent reply other threads:[~2020-05-27 14:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 18:59 [PR PATCH] " MarleDK
2020-04-27 19:22 ` [PR PATCH] [Updated] " MarleDK
2020-04-27 22:51 ` Duncaen
2020-04-28 9:34 ` MarleDK
2020-04-28 11:10 ` pullmoll
2020-04-28 11:16 ` pullmoll
2020-04-28 18:23 ` MarleDK
2020-05-15 21:12 ` pullmoll
2020-05-25 9:03 ` [PR PATCH] [Updated] " MarleDK
2020-05-25 9:06 ` MarleDK
2020-05-26 6:36 ` [PR PATCH] [Updated] " MarleDK
2020-05-27 5:46 ` MarleDK
2020-05-27 5:48 ` MarleDK
2020-05-27 14:29 ` pullmoll [this message]
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=20200527142957.ujC0dtNXhvqtLtH_FOBzypBQ_R9QLzrFEeSTPOWMc8w@z \
--to=pullmoll@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).