From: Markus Volk <f_l_k@t-online.de>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Markus Volk <f_l_k@t-online.de>,
meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH 2/2] libvirt: update from fuse2 to fuse3
Date: Thu, 24 Aug 2023 10:13:43 +0200 [thread overview]
Message-ID: <VUYVZR.QDF6U5KVLHEQ2@t-online.de> (raw)
In-Reply-To: <CADkTA4PbL2QQDJDS6Jwhc0cvUq-thQ1Bt3onDP5tXa7QAZk7_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]
I wrote a few lines about why I would like to do this.
On Wed, Aug 23 2023 at 10:28:02 PM -04:00:00, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> I'm ok with the change, but we need to document why we are making
> the switch in the commit log.
>
> Bruce
>
> On Tue, Aug 22, 2023 at 5:55 PM Markus Volk <f_l_k@t-online.de
> <mailto:f_l_k@t-online.de>> wrote:
>>
>> Signed-off-by: Markus Volk <f_l_k@t-online.de
>> <mailto: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
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#8220):
>> <https://lists.yoctoproject.org/g/meta-virtualization/message/8220>
>> Mute This Topic:
>> <https://lists.yoctoproject.org/mt/100903758/1050810>
>> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
>> <mailto:meta-virtualization+owner@lists.yoctoproject.org>
>> Unsubscribe:
>> <https://lists.yoctoproject.org/g/meta-virtualization/unsub>
>> [bruce.ashfield@gmail.com <mailto:bruce.ashfield@gmail.com>]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
[-- Attachment #2: Type: text/html, Size: 2672 bytes --]
prev parent reply other threads:[~2023-08-24 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 21:55 [meta-virtualization][PATCH 1/2] libvirt-glib: fix introspection and documentation build Markus Volk
2023-08-22 21:55 ` [meta-virtualization][PATCH 2/2] libvirt: update from fuse2 to fuse3 Markus Volk
2023-08-24 2:28 ` Bruce Ashfield
2023-08-24 8:13 ` Markus Volk [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=VUYVZR.QDF6U5KVLHEQ2@t-online.de \
--to=f_l_k@t-online.de \
--cc=bruce.ashfield@gmail.com \
--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).