From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Compile terminfo description when building
Date: Fri, 22 Jul 2022 15:53:43 +0200 [thread overview]
Message-ID: <20220722135343.SjlxfUgD29vz6_55zISub5SmSu63RNtZhqEVtxe7SjI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38179@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/38179#issuecomment-1192600341
Comment:
> > I think that has been done previously for foot [#36884 (comment)](https://github.com/void-linux/void-packages/pull/36884#issuecomment-1131836929)
>
> This is interesting. But now `ncurses-terminfo` doesn't contain terminfo descriptions for `foot`. I think adding `foot-terminfo` as a dependency of `ncurses-term` would be better. When I install `ncurses-term`, I expect to get all terminfo files, not only ones that do not have its own package.
We can't do that. ncurses is a very core package and shouldn't have any dependencies. Currently it doesn't, so building it is quick even with `-N`. What you are proposing would make the build take hours and most likely introduce a lot of build cycles, for example `ncurses (ncurses-term) -> foot (foot-terminfo) -> ncurses (ncurses-devel)`
next prev parent reply other threads:[~2022-07-22 13:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 22:04 [PR PATCH] " meator
2022-07-21 22:11 ` [PR PATCH] [Updated] " meator
2022-07-22 5:27 ` meator
2022-07-22 5:47 ` meator
2022-07-22 5:51 ` classabbyamp
2022-07-22 7:25 ` meator
2022-07-22 13:53 ` paper42 [this message]
2022-07-22 13:54 ` paper42
2022-07-22 17:39 ` [PR PATCH] [Updated] " meator
2022-07-22 17:41 ` meator
2022-07-22 17:41 ` meator
2022-07-22 17:48 ` meator
2022-07-22 17:57 ` [PR PATCH] [Updated] " meator
2022-07-22 17:59 ` meator
2022-07-23 15:08 ` sgn
2022-07-23 21:02 ` [PR PATCH] [Updated] " meator
2022-09-30 0:28 ` classabbyamp
2022-09-30 17:20 ` meator
2022-09-30 17:21 ` [PR PATCH] [Updated] " meator
2022-09-30 20:12 ` classabbyamp
2022-09-30 20:14 ` classabbyamp
2022-10-01 13:08 ` [PR PATCH] [Updated] " meator
2022-10-01 16:21 ` classabbyamp
2022-10-01 16:45 ` [PR PATCH] [Updated] " meator
2022-10-01 16:48 ` meator
2022-10-01 21:51 ` [PR PATCH] [Merged]: " classabbyamp
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=20220722135343.SjlxfUgD29vz6_55zISub5SmSu63RNtZhqEVtxe7SjI@z \
--to=paper42@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).