From: Peter Korsgaard <peter@korsgaard.com>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/bubblewrap: security bump to version 0.12.0
Date: Mon, 14 Sep 2026 07:30:12 +0200 [thread overview]
Message-ID: <8733vcwgbf.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260913231418.GE163018209104943@igalia.com> (Adrian Perez de Castro's message of "Sun, 13 Sep 2026 23:14:18 +0200")
>>>>> "Adrian" == Adrian Perez de Castro <aperez@igalia.com> writes:
Hi,
>> > BUBBLEWRAP_CONF_OPTS = \
>> > + -Dassume_kernel=$(LINUX_VERSION_PROBED) \
>>
>> What happens if the config does not build a Linux kernel (then this
>> presumably expands to -Dassume_kernel=)?
> Exactly, and the empty value is the default as well for the option. In
> that case the fallback code for older kernel versions is enabled for the
> Bubblewrap build. IMO that is the right thing to do because we cannot
> guess which kernel version will be used at runtime.
OK, great - It wasn't clear to me if that was the behaviour of the
bubblewrap build system, maybe a note in the commit message would have
been good.
And I agree, we shouldn't assume any specific kernel version if we do
not build one.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-09-14 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 9:52 [Buildroot] [PATCH] package/bubblewrap: security bump to version 0.12.0 Adrian Perez de Castro
2026-09-10 20:01 ` Julien Olivain via buildroot
2026-09-11 0:07 ` Adrian Perez de Castro
2026-09-11 13:32 ` Peter Korsgaard
2026-09-13 21:14 ` Adrian Perez de Castro
2026-09-14 5:30 ` Peter Korsgaard [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=8733vcwgbf.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=aperez@igalia.com \
--cc=buildroot@buildroot.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