All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nayab Sayed via buildroot <buildroot@buildroot.org>
Cc: Nayab Sayed <nayabbasha.sayed@microchip.com>
Subject: Re: [Buildroot] [PATCH] package/busybox: refresh busybox.config
Date: Wed, 1 May 2024 22:18:38 +0200	[thread overview]
Message-ID: <20240501221838.07cb2684@windsurf> (raw)
In-Reply-To: <20240426-refresh-busybox-config-v1-1-c70cb5b60243@microchip.com>

Hello Nayab,

+Arnout in Cc (question below).

On Fri, 26 Apr 2024 14:10:58 +0530
Nayab Sayed via buildroot <buildroot@buildroot.org> wrote:

> Refresh busybox.config to current version (1.36.1) default values.
> 
> Signed-off-by: Nayab Sayed <nayabbasha.sayed@microchip.com>
> ---
> When `make busybox-update-config` is executed, the config
> CONFIG_UDHCPC6_DEFAULT_SCRIPT became empty. But it's updated to reuse the
> value from earlier bump as mentioned in the commit d68b617993bd
> (package/busybox: update to 1.36.0).

Arnout: I don't really understand the reasoning in commit d68b617993bd.
The commit log says:

    Refresh busybox.config. All configs are set to the new defaults, except
    for CONFIG_UDHCPC_DEFAULT_SCRIPT: for this one, reuse the script we also
    use for DHCPv4. This is matches the behaviour previous to the bump,
    where we had a single script handling both.

Did you mean to say CONFIG_UDHCPC6_DEFAULT_SCRIPT instead?

In the commit, you do:

+CONFIG_UDHCPC6_DEFAULT_SCRIPT="/usr/share/udhcpc/default.script"

But then, why do we do that? udhcpc6 is not enabled in our
busybox.config. Due to this, when we refresh busybox.config, this
CONFIG_UDHCPC6_DEFAULT_SCRIPT gets dropped.

> @@ -336,7 +336,7 @@ CONFIG_TEST=y
>  CONFIG_TEST1=y
>  CONFIG_TEST2=y
>  CONFIG_FEATURE_TEST_64=y
> -# CONFIG_TIMEOUT is not set
> +CONFIG_TIMEOUT=y

Nayab: this doesn't show up here when I refresh the file. Are you sure
this isn't a custom change on your side, unrelated to the Busybox file
refresh?

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-05-01 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  8:40 [Buildroot] [PATCH] package/busybox: refresh busybox.config Nayab Sayed via buildroot
2024-05-01 20:18 ` Thomas Petazzoni via buildroot [this message]
2024-05-06 10:10   ` Nayab Sayed via buildroot
2024-05-09 20:57   ` Arnout Vandecappelle via buildroot
2024-05-09 21:15     ` Thomas Petazzoni via buildroot

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=20240501221838.07cb2684@windsurf \
    --to=buildroot@buildroot.org \
    --cc=nayabbasha.sayed@microchip.com \
    --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 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.