From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ncurses-term file conflicts
Date: Wed, 25 Nov 2020 21:01:41 +0100 [thread overview]
Message-ID: <20201125200141.MoF38OIMGwTmvNeOHWxOwMrmTQtxfs14nUe6siHtL5U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26700@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/26700#issuecomment-733920451
Comment:
Arch and Alpine both do the opposite. The ncurses package provides these terminfo files. The alacritty packages in both decline to manually copy and compile the provided terminfo. The dvtm packages in both explicitly remove the terminfo after installation. I didn't bother looking at the other two.
I'm ok with removing the specific terminfo packages, letting them pull in ncurses-term instead. I'm also okay with noextract rules in the individual packages because they don't require specific knowledge. It's just a way to say, "I don't care who provides these files, I take precedence so don't allow anybody else to overwrite these." Going the other direction, removing specific files from ncurses because we want to defer to the specific packages, requires too much special casing and distributed knowledge for my taste.
next prev parent reply other threads:[~2020-11-25 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 15:50 [ISSUE] " ahesford
2020-11-25 15:56 ` ericonr
2020-11-25 16:05 ` ahesford
2020-11-25 16:54 ` ericonr
2020-11-25 20:01 ` ahesford [this message]
2021-08-08 14:15 ` ericonr
2022-04-30 2:14 ` github-actions
2022-04-30 3:53 ` ahesford
2022-04-30 3:53 ` [ISSUE] [CLOSED] " ahesford
2022-05-01 19:08 ` ericonr
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=20201125200141.MoF38OIMGwTmvNeOHWxOwMrmTQtxfs14nUe6siHtL5U@z \
--to=ahesford@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).