From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: alacritty, st, dvtm: prevent ncurses-term from installing conflicting files
Date: Wed, 25 Nov 2020 17:13:09 +0100 [thread overview]
Message-ID: <20201125161309.A85IRIFuuO6Kd7h8WS9KrqbtLclSx4MhYIDvKSqtqvY@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: 846 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/26701#issuecomment-733803669
Comment:
Right, this won't prevent `ncurses-term` from installing those files in advance or simultaneously, and `xbps-pkgdb -a` will still complain after the fact if `ncurses-term` is installed before the rules take effect. At least this prevents reinstallation or upgrades of `ncurses-term` from overwriting the files, and I believe `xbps-remove ncurses-term` will leave the changed files in place.
Of course, because XBPS extracts packages in lexicographic order, `xbps-install alacritty-terminfo ncurses-term` and `xbps-install dvtm ncurses-term` will cause the `ncurses-term` versions to overwrite the specific versions the first time, while `xbps-install st-terminfo ncurses-term` will behave "correctly".
next prev parent reply other threads:[~2020-11-25 16:13 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 [this message]
2020-11-25 16:56 ` ericonr
2020-12-09 21:09 ` ahesford
2020-12-09 21:09 ` [PR PATCH] [Closed]: " ahesford
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=20201125161309.A85IRIFuuO6Kd7h8WS9KrqbtLclSx4MhYIDvKSqtqvY@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).