From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Markus Volk <f_l_k@t-online.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] neard: dont pull in wpa-supplicant unconditionally
Date: Mon, 16 Jan 2023 17:56:22 +0000 [thread overview]
Message-ID: <b5b5df9998b2a854bc7d4d9f038428638c05fdbf.camel@linuxfoundation.org> (raw)
In-Reply-To: <II9LOR.Y1Q7EACQVKAA1@t-online.de>
On Mon, 2023-01-16 at 18:20 +0100, Markus Volk wrote:
> Yes, that's right, of course. What would be the preferred way to deal
> with this. The dependency on wpa-supplicant is a bit annoying. Should
> I use a bbappend to remove it, or is the RRECOMMEND on wpa-supplicant
> perhaps removable from the neard recipe?
It might be time to add something to meta/conf/distro/includes/default-
providers.inc along the lines of:
VIRTUAL-RUNTIME_wireless-daemon ?= "wpa-supplicant"
I don't like these but probably need something more central/standard...
Cheers,
Richard
prev parent reply other threads:[~2023-01-16 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 16:43 [oe-core][PATCH] neard: dont pull in wpa-supplicant unconditionally Markus Volk
2023-01-16 16:47 ` Richard Purdie
2023-01-16 16:49 ` Markus Volk
2023-01-16 17:03 ` Richard Purdie
2023-01-16 17:20 ` Markus Volk
2023-01-16 17:47 ` Jose Quaresma
2023-01-16 17:56 ` Richard Purdie [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=b5b5df9998b2a854bc7d4d9f038428638c05fdbf.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=f_l_k@t-online.de \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.