From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] infra/pkg-kconfig: Be sure to reconfigure the package on foo-reconfigure
Date: Fri, 16 Sep 2016 19:05:17 +0200 [thread overview]
Message-ID: <20160916190517.01d3dd5a@free-electrons.com> (raw)
In-Reply-To: <1473806117-3858-1-git-send-email-yann.morin.1998@free.fr>
Hello,
On Wed, 14 Sep 2016 00:35:17 +0200, Yann E. MORIN wrote:
> +# Force olddefconfig again on -reconfigure
> +$(1)-clean-for-reconfigure: $(1)-clean-kconfig-for-reconfigure
> +
> +$(1)-clean-kconfig-for-reconfigure:
> + rm -f $$($(2)_DIR)/.stamp_kconfig_fixup_done
I was about to apply this, but in fact, I'm not sure I agree.
<foo>-reconfigure is supposed to re-do the configuration step entirely.
For example, with an autotools package, if I change the value of
<pkg>_CONF_OPTS and then do make <foo>-reconfigure, the configuration
is done again, with the new <pkg>_CONF_OPTS.
Here, what you're doing is that you're only re-doing the "fixup" of
the .config, but you're not re-loading the configuration from the
original defconfig or full config file. This means that if the user
changes the defconfig and does "make linux-reconfigure", it won't
reload the defconfig.
Unless my analysis is wrong, I think the patch should be changed to
re-do the configuration step entirely.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-16 17:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 22:35 [Buildroot] [PATCH] infra/pkg-kconfig: Be sure to reconfigure the package on foo-reconfigure Yann E. MORIN
2016-09-13 22:59 ` Vivien Didelot
2016-09-13 23:29 ` Arnout Vandecappelle
2016-09-14 7:27 ` Thomas De Schampheleire
2016-09-14 9:01 ` Thomas Petazzoni
2016-09-14 17:42 ` Thomas De Schampheleire
2016-09-14 18:32 ` Yann E. MORIN
2016-09-14 18:38 ` Yann E. MORIN
2016-09-16 17:05 ` Thomas Petazzoni
2016-09-16 17:05 ` Thomas Petazzoni [this message]
2016-09-16 17:17 ` Yann E. MORIN
2016-09-16 17:56 ` Yann E. MORIN
2016-09-16 19:02 ` Yann E. MORIN
2016-09-17 12:42 ` Thomas Petazzoni
2016-09-17 12:53 ` Yann E. MORIN
2016-09-17 13:17 ` Thomas Petazzoni
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=20160916190517.01d3dd5a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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