Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: binfmt handling improvements, qemu: update to 9.0.1
Date: Mon, 17 Jun 2024 22:13:34 +0200	[thread overview]
Message-ID: <20240617201334.9E2F4229D4@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50838@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

There's a merged pull request on the void-packages repository

binfmt handling improvements, qemu: update to 9.0.1
https://github.com/void-linux/void-packages/pull/50838

Description:
This cleans up a lot of the binfmt handling in triggers and especially qemu-user-static.

- `update-binfmts --import` is a lot cleaner than `update-binfmts --install`
- moves the important data out of the install script and into the package itself (`/usr/share/binfmts`)
- allows the `binfmts` trigger to be detected automatically
- old behaviour kept around for compatibility, with signficant cleanups to the code
- qemu provides a script to generate binfmt definitions in the format `update-binfmts --import` understands, removing a bunch of junk from the template
- these definition files are simple enough that we can generate it for wine during build

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**



      parent reply	other threads:[~2024-06-17 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-15 19:00 [PR PATCH] " classabbyamp
2024-06-16  7:50 ` [PR PATCH] [Updated] " classabbyamp
2024-06-16 18:38 ` classabbyamp
2024-06-17 20:13 ` classabbyamp [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=20240617201334.9E2F4229D4@inbox.vuxu.org \
    --to=classabbyamp@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).