From: Markus Volk <f_l_k@t-online.de>
To: meta-virtualization@lists.yoctoproject.org
Subject: [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3
Date: Thu, 24 Aug 2023 10:10:02 +0200 [thread overview]
Message-ID: <20230824081002.6730-1-f_l_k@t-online.de> (raw)
Using fuse2 and fuse3 in the same environment can be problematic. Most
projects I know of now support fuse3. ostree, flatpak, xdg-desktop-portal
and some other recipes in meta-openembedded are configured to use fuse3 and
libvirt is also able to do so.
This commit switches libvirt to fuse3 to reduce the number of recipes that still use
the old version.
Signed-off-by: Markus Volk <f_l_k@t-online.de>
---
recipes-extended/libvirt/libvirt_9.2.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-extended/libvirt/libvirt_9.2.0.bb b/recipes-extended/libvirt/libvirt_9.2.0.bb
index 5e70470..9b5b2de 100644
--- a/recipes-extended/libvirt/libvirt_9.2.0.bb
+++ b/recipes-extended/libvirt/libvirt_9.2.0.bb
@@ -156,7 +156,7 @@ PACKAGECONFIG[selinux] = "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
PACKAGECONFIG[python] = ",,python3,"
PACKAGECONFIG[sasl] = "-Dsasl=enabled,-Dsasl=disabled,cyrus-sasl,cyrus-sasl"
PACKAGECONFIG[numactl] = "-Dnumactl=enabled,-Dnumactl=disabled,numactl,"
-PACKAGECONFIG[fuse] = "-Dfuse=enabled,-Dfuse=disabled,fuse,"
+PACKAGECONFIG[fuse] = "-Dfuse=enabled,-Dfuse=disabled,fuse3,"
PACKAGECONFIG[audit] = "-Daudit=enabled,-Daudit=disabled,audit,"
PACKAGECONFIG[libcap-ng] = "-Dcapng=enabled,-Dcapng=disabled,libcap-ng,"
PACKAGECONFIG[wireshark] = "-Dwireshark_dissector=enabled,-Dwireshark_dissector=disabled,wireshark libwsutil,"
--
2.41.0
next reply other threads:[~2023-08-24 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 8:10 Markus Volk [this message]
2023-08-27 13:28 ` [meta-virtualization][PATCHv2] libvirt: update from fuse2 to fuse3 Bruce Ashfield
2023-08-27 13:30 ` Bruce Ashfield
2023-08-28 2:43 ` Markus Volk
2023-08-28 10:17 ` Bruce Ashfield
2023-08-28 17:46 ` Markus Volk
2023-08-29 1:49 ` Bruce Ashfield
2023-08-29 6:18 ` Markus Volk
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=20230824081002.6730-1-f_l_k@t-online.de \
--to=f_l_k@t-online.de \
--cc=meta-virtualization@lists.yoctoproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).