From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ncurses: add libtinfo.so
Date: Tue, 28 Apr 2020 13:16:27 +0200 [thread overview]
Message-ID: <20200428111627.SV93fCSZmzz0Z4YdvbKHpehRqSQ6uVIaeDgln5HCz1o@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: 1372 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21409#issuecomment-620539507
Comment:
@Duncaen I completely forgot about #11718 . Strange how a single year of events can perfuse your mind with vacuities.
I think it would be worth a try to vmove `libtinfo.so.*` in a separate `tinfo_packge()` function and also add a `tinfo-devel_package()` which vmoves `libtinfo.so`.
To really split `ncurses` from `tinfo` perhaps we should also split out the header files into an e.g. `ncurses-headers_package()` and depend on this from both, `ncurses-devel` and `tinfo-devel`.
This way no package depending on `ncurses-devel` should see anything of `tinfo` and vice-versa, and then packages like `Stack` can explicitly depend on `tinfo`. Actually `ncurses-devel` and `tinfo-devel` need to be conflicting packages.
In any case this PR has to be tested thoroughly in how it changes (it should not!) how packages depending on `ncurses` are built.
@MarleDK your observations make me think that `ncurses` should be built twice, once with (for tinfo) and once without (for ncurses) the `--with-termininfo` option. OTOH this could complicate the `ncurses` template too much. Simply creating a separate `tinfo` or `libtinfo` package and its `-devel` subpackage, and not touch `ncurses` at all, looks like the better choice.
next prev parent reply other threads:[~2020-04-28 11:16 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 [this message]
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 ` [PR PATCH] [Merged]: " pullmoll
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=20200428111627.SV93fCSZmzz0Z4YdvbKHpehRqSQ6uVIaeDgln5HCz1o@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).