public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: vishal.gupta_1@philips.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/1] wpa-supplicant: fix sed expression
Date: Thu, 08 Jan 2026 14:12:28 +0000	[thread overview]
Message-ID: <421adaf51e6bd83585166b0e3292402bcb319650.camel@pbarker.dev> (raw)
In-Reply-To: <250823.1766152615641090465@lists.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]

On Fri, 2025-12-19 at 05:56 -0800, vishal.gupta_1 via
lists.openembedded.org wrote:
> Hi Alexander,
> 
> In the do_configure function current intention of implementation is to first delete it when we copying and then depending on the PACKAGECONFIG assign it with correct value.
> As delete is failed because the line start with "#" we will have two CONFIG_TLS value in final ".config" file
> 
> one, at some where middle of the file
> #CONFIG_TLS=openssl
> 
> second, depending on package config, at the end of file as it's an append operation.
> CONFIG_TLS=openssl / gnutls
> 
> do_configure () {
> ${MAKE} -C wpa_supplicant clean
> sed -e '/^#\?CONFIG_TLS=/d' <wpa_supplicant/defconfig >wpa_supplicant/.config
> if ${@ bb.utils.contains('PACKAGECONFIG', 'openssl', 'true', 'false', d) }; then
> echo 'CONFIG_TLS=openssl' >>wpa_supplicant/.config
> elif ${@ bb.utils.contains('PACKAGECONFIG', 'gnutls', 'true', 'false', d) }; then
> echo 'CONFIG_TLS=gnutls' >>wpa_supplicant/.config
> sed -i -e 's/\(^CONFIG_DPP=\)/#\1/' \
> -e 's/\(^CONFIG_EAP_PWD=\)/#\1/' \
> -e 's/\(^CONFIG_SAE=\)/#\1/' wpa_supplicant/.config
> fi
> 
> So with this change there will be only one "CONFIG_TLS=<value>" option.

Looking at the wpa_supplicant README file [1]:

  Configuration options are text lines using following
  format: CONFIG_<option>=y. Lines starting with # are considered
  comments and are ignored.

[1]: https://git.w1.fi/cgit/hostap/tree/wpa_supplicant/README

So, leaving the comment line with the default CONFIG_TLS value isn't a
problem.

Best regards,

-- 
Paul Barker


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2026-01-08 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 12:49 [PATCH 1/1] wpa-supplicant: fix sed expression Vishal Gupta
2025-12-19 13:30 ` [OE-core] " Alexander Kanavin
2025-12-19 13:56   ` vishal.gupta_1
2026-01-08 14:12     ` Paul Barker [this message]
2026-01-09 16:33       ` vishal.gupta_1

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=421adaf51e6bd83585166b0e3292402bcb319650.camel@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=vishal.gupta_1@philips.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