Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/network-manager: rework jansson handling
Date: Tue, 20 Oct 2026 18:38:39 +0200	[thread overview]
Message-ID: <8733u09vjk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20261020135455.1595899-2-thomas.petazzoni@bootlin.com> (Thomas Petazzoni via buildroot's message of "Tue, 20 Oct 2026 15:54:54 +0200")

>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:

 > jansson is needed for BR2_PACKAGE_NETWORK_MANAGER_OVS (which selects
 > BR2_PACKAGE_JANSSON), but practicaly speaking, network-manager's
 > meson.build detects jansson regardless of ovs=true. So we make this
 > jansson optional dependency explicit.

 > This commit doesn't fix anything, it only makes the dependency more
 > explicit.

 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-10-20 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 13:54 [Buildroot] [PATCH 1/2] package/network-manager: fix build when jansson is enabled Thomas Petazzoni via buildroot
2026-10-20 13:54 ` [Buildroot] [PATCH 2/2] package/network-manager: rework jansson handling Thomas Petazzoni via buildroot
2026-10-20 16:38   ` Peter Korsgaard [this message]
2026-10-20 16:38 ` [Buildroot] [PATCH 1/2] package/network-manager: fix build when jansson is enabled Peter Korsgaard
2026-10-20 16:39   ` Peter Korsgaard

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=8733u09vjk.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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