From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ncurses-term file conflicts
Date: Sat, 30 Apr 2022 05:53:43 +0200 [thread overview]
Message-ID: <20220430035343.vvGye8iYO9zu1xj1RuI47cBD_z76VrS-exYUpoOuItA@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: 1431 bytes --]
Closed issue by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/26700
Description:
The `ncurses-term` package ships some terminfo databases that conflict with files installed by terminal-specific packages:
- `alacritty-terminfo`
- `dvtm`
- `fbterm`
- `st-terminfo`
The `fbterm` package installs the compiled `/usr/share/terminfo/f/fbterm` directly, which is an outright conflict with a matching file in `ncurses-term`. The other three install source files (`*.info`) that do not directly conflict, but the `INSTALL` scripts compile these and overwrite corresponding files in `ncurses-term`; the `REMOVE` scripts of these packages remove the files.
This, at least, causes unnecessary noise in `xbps-pkgdb -a` output when both `ncurses-term` and terminal-specific packages are installed. More problematic is the potential breakage or degradation that may result when installing or reinstalling `ncurses-term`, which can replace newer databases that might be required by terminal emulators.
There doesn't appear to be a good way to handle this gracefully and automatically. I work around this issue for `alacritty` by adding XBPS `noextract` rules for `/usr/share/terminfo/a/alacritty{,-direct,+common}`. One possibility would be installing similar rules in `/usr/share/xbps.d` in each package that installs terminal-specific files, but not sure what happens on for `xbps<0.58`.
next prev parent reply other threads:[~2022-04-30 3:53 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
2021-08-08 14:15 ` ericonr
2022-04-30 2:14 ` github-actions
2022-04-30 3:53 ` ahesford
2022-04-30 3:53 ` ahesford [this message]
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=20220430035343.vvGye8iYO9zu1xj1RuI47cBD_z76VrS-exYUpoOuItA@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).