From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: alacritty-terminfo fails script, because ncurses is not installed
Date: Thu, 21 Jul 2022 09:17:01 +0200 [thread overview]
Message-ID: <20220721071701.8_AhOxMEbBP8VIeG52AdJqckkLjWIXTywVUIzlW0kcQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34392@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/issues/34392#issuecomment-1191131393
Comment:
[`dvtm`](https://github.com/void-linux/void-packages/blob/master/srcpkgs/dvtm/INSTALL) and [`alacritty-terminfo`](https://github.com/void-linux/void-packages/blob/master/srcpkgs/alacritty/alacritty-terminfo.INSTALL) package the `.info` files with them and they are compiled in `INSTALL` script when they are being installed. These should be he only two packages that are doing this. I don't know why they don't simply compile them while building and then ship the compiled files, but I think the maintainers of these packages wouldn't have chosen this more complicated way of packaging terminfo without a reason.
Since these files are compiled on install, you should both have the `.info` and the compiled version @erwin. If not, than there is a problem with the `alacritty-terminfo` and it should be fixed.
And it might be more visible if you would create a separate issue for this if there are any problems with this rather than commenting on a old and closed issue.
next prev parent reply other threads:[~2022-07-21 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 12:52 [ISSUE] " hasufell
2021-12-11 3:19 ` [ISSUE] [CLOSED] " ericonr
2022-07-21 2:50 ` erwin
2022-07-21 7:17 ` meator [this message]
2022-07-21 7:44 ` erwin
2022-07-21 8:25 ` meator
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=20220721071701.8_AhOxMEbBP8VIeG52AdJqckkLjWIXTywVUIzlW0kcQ@z \
--to=meator@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).