From: TeusLollo <TeusLollo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Updating p7zip-22.01 package break because of missing /usr/bin/7z
Date: Thu, 22 Dec 2022 15:44:32 +0100 [thread overview]
Message-ID: <20221222144432.bfWmkaVC2DlfhAYXA_zmoMzTmOU-eU9ObEFzv7Z0WOc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41209@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
New comment by TeusLollo on void-packages repository
https://github.com/void-linux/void-packages/issues/41209#issuecomment-1362923545
Comment:
I'm still not very familiar with `xbps`, but it looks to me also that having some of kind of pre-transaction hooking mechanism to issue special commands to would also simplify things when such potential conflicts occur.
This `xbps` fork, for example, claims to have both a pre-transaction and post-transaction hooking mechanism akin to, I speculate, `pacman`.
https://github.com/pandom79/xbps/tree/new-xbps-pkgkit-2.0
Mind you I haven't tested nothing of it, nor I have audited the actual coding quality, nor I know anything about this user.
Compared to Arch, I'm actually impressed at how hooking mechanisms are scarcely necessary overall, and how `xbps` is more resilient than `pacman` overall.
Still, if such edge cases become relevant enough, I guess transaction hooks may become more of a necessity.
Otherwise, sticking to template-based checks as it's been done here may also work in most cases, I guess.
prev parent reply other threads:[~2022-12-22 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 22:18 [ISSUE] Recent introduction of 7zip-22.01 package broke functionalities into xarchiver-0.5.4.20_1 and possibly further packages too TeusLollo
2022-12-21 1:37 ` sgn
2022-12-21 1:42 ` sgn
2022-12-21 1:45 ` sgn
2022-12-21 1:49 ` sgn
2022-12-21 2:04 ` [ISSUE] [CLOSED] " sgn
2022-12-21 20:58 ` Updating p7zip-22.01 package break because of missing /usr/bin/7z r-ricci
2022-12-22 14:44 ` TeusLollo [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=20221222144432.bfWmkaVC2DlfhAYXA_zmoMzTmOU-eU9ObEFzv7Z0WOc@z \
--to=teuslollo@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).