From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: alacritty, st, dvtm: prevent ncurses-term from installing conflicting files
Date: Wed, 09 Dec 2020 22:09:04 +0100 [thread overview]
Message-ID: <20201209210904.6RUv_hTMhVHWgFDl5RBMPJEVYb207hhmTRfjN1FeD2I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26701@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
There's a closed pull request on the void-packages repository
alacritty, st, dvtm: prevent ncurses-term from installing conflicting files
https://github.com/void-linux/void-packages/pull/26701
Description:
This is an attempt to address file conflicts in Issue #26700 by adding `noextract` rules to packages that install specific terminfo definitions and then compile these at locations that conflict with files installed by `ncurses-term`. We should definitely prefer these specific versions when they are installed.
I'm not sure what `xbps<0.58` does when it encounters `noextract` definitions. This isn't the most elegant solution, but it may be the only workable solution we currently have to the conflicts here. Any other solution would seem to require knowledge in the `ncurses` template of specific templates that install conflicting files, which is uglier.
prev parent reply other threads:[~2020-12-09 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 16:00 [PR PATCH] " ahesford
2020-11-25 16:03 ` ericonr
2020-11-25 16:04 ` ericonr
2020-11-25 16:08 ` [PR PATCH] [Updated] " ahesford
2020-11-25 16:13 ` ahesford
2020-11-25 16:56 ` ericonr
2020-12-09 21:09 ` ahesford
2020-12-09 21:09 ` ahesford [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=20201209210904.6RUv_hTMhVHWgFDl5RBMPJEVYb207hhmTRfjN1FeD2I@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).