Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: fwupd: change deps
Date: Tue, 09 Nov 2021 20:39:35 +0100	[thread overview]
Message-ID: <20211109193935.tBQkhYRxRlSOxmNCEiS6Kn6EipZV_KNj2ploiMuQ7NM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32932@inbox.vuxu.org>

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

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

fwupd: change deps
https://github.com/void-linux/void-packages/pull/32932

Description:
drop dep on udisks2, add dep on dbus
drop -Dintrospection=true, which is default
built and checked on x86_64-musl

udisks2 brings in a lot of bloat, just to discover the ESP partition, but it actually does not do the job,
so it would be simpler to just let the user take care of that. (That's also what Alpine does btw.)
Notice even with udisks, I currently have to do
`mount -t efivarfs efivarfs /sys/firmware/efi/efivars`
otherwise fwupd does not find the bios to update.
Instead, dbus seems to be a needed dependency.

  parent reply	other threads:[~2021-11-09 19:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11 15:18 [PR PATCH] fwudp: change deps and config dkwo
2021-09-11 19:44 ` ericonr
2021-09-12  6:30 ` [PR PATCH] [Updated] " dkwo
2021-09-15  7:36 ` fwupd: change deps dkwo
2021-09-16  1:27 ` ericonr
2021-09-16 11:35 ` [PR PATCH] [Updated] " dkwo
2021-09-16 11:58 ` dkwo
2021-09-16 18:53 ` ericonr
2021-09-16 19:30 ` [PR PATCH] [Updated] " dkwo
2021-09-16 19:31 ` dkwo
2021-10-07  8:24 ` [PR PATCH] [Updated] " dkwo
2021-10-07  8:36 ` dkwo
2021-11-09 12:22 ` dkwo
2021-11-09 19:39 ` ericonr [this message]
2021-11-09 19:40 ` ericonr
2021-11-10  8:59 ` dkwo

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=20211109193935.tBQkhYRxRlSOxmNCEiS6Kn6EipZV_KNj2ploiMuQ7NM@z \
    --to=ericonr@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).