From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 5 RFC] uclibc/busybox: fix handling of configuration file
Date: Wed, 25 Jun 2014 08:06:45 +0200 [thread overview]
Message-ID: <53AA66F5.3090706@mind.be> (raw)
In-Reply-To: <patchbomb.1403444739@localhost>
Hi Thomas,
On 22/06/14 15:45, Thomas De Schampheleire wrote:
>
> This patch series reworks the uclibc/busybox config file handling, based on
> following requirements:
>
> - neither foo-menuconfig nor foo-update-config should have a dependency on
> the toolchain (which means we cannot depend on foo-configure)
> - 'clean foo-menuconfig' should start from the specified (custom) config
> file
> - 'foo-menuconfig foo-update-config' should preserve the changes made in the
> menuconfig step (this problem is reported for uclibc with bug #7154
> (https://bugs.busybox.net/show_bug.cgi?id=7154).
I agree with these requirements. With of course the additional requirement
mentioned by ThomasP:
- 'make foo-menuconfig; make foo-menuconfig' should preserve the changes made in
the menuconfig step.
However, I think it would be better to add infrastructure for kconfig packages,
instead of repeating the work for uclibc, busybox, linux and barebox. I was
thinking along the lines of:
$(eval $(generic-package))
LINUX_KCONFIG_TARGETS = menuconfig xconfig gconfig nconfig
LINUX_HAS_DEFCONFIG = YES
$(eval $(kconfig-package))
Regards,
Arnout
>
> The series currently covers uclibc and busybox only, while the problem seems
> to be present for linux too. It is submitted as an RFC for this reason, as
> I'm unsure if there are comments on the approach.
>
> Thanks for your feedback...
>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
>
> ---
> package/busybox/busybox.mk | 28 +++++++++++++++++++---------
> package/uclibc/uclibc.mk | 16 +++++++++++++---
> 2 files changed, 32 insertions(+), 12 deletions(-)
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-06-25 6:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 13:45 [Buildroot] [PATCH 0 of 5 RFC] uclibc/busybox: fix handling of configuration file Thomas De Schampheleire
2014-06-22 13:45 ` [Buildroot] [PATCH 1 of 5 RFC] uclibc: menuconfig: take into account initial settings from config file Thomas De Schampheleire
2014-06-22 14:05 ` Yann E. MORIN
2014-06-22 16:52 ` Thomas Petazzoni
2014-06-22 17:23 ` Thomas De Schampheleire
2014-06-22 17:29 ` Danomi Manchego
2014-06-22 18:52 ` Thomas De Schampheleire
2014-06-22 19:07 ` Danomi Manchego
2014-06-24 18:35 ` Thomas De Schampheleire
2014-06-25 6:16 ` Arnout Vandecappelle
2014-06-30 19:31 ` Thomas De Schampheleire
2014-07-01 6:09 ` Arnout Vandecappelle
2014-07-01 8:35 ` Thomas De Schampheleire
2014-06-22 13:45 ` [Buildroot] [PATCH 2 of 5 RFC] uclibc: update-config: preserve freshly configured settings Thomas De Schampheleire
2014-06-22 14:07 ` Yann E. MORIN
2014-06-22 13:45 ` [Buildroot] [PATCH 3 of 5 RFC] busybox: fix typo overwritting Thomas De Schampheleire
2014-06-22 13:57 ` Yann E. MORIN
2014-06-22 13:45 ` [Buildroot] [PATCH 4 of 5 RFC] busybox: menuconfig: take into account initial settings from config file Thomas De Schampheleire
2014-06-22 14:10 ` Yann E. MORIN
2014-06-22 13:45 ` [Buildroot] [PATCH 5 of 5 RFC] busybox: update-config: preserve freshly configured settings Thomas De Schampheleire
2014-06-22 14:14 ` Yann E. MORIN
2014-06-22 14:22 ` Thomas De Schampheleire
2014-06-22 14:46 ` Yann E. MORIN
2014-06-25 6:06 ` Arnout Vandecappelle [this message]
2014-06-25 19:24 ` [Buildroot] [PATCH 0 of 5 RFC] uclibc/busybox: fix handling of configuration file Thomas De Schampheleire
2014-06-29 8:13 ` Thomas De Schampheleire
2014-06-29 8:20 ` Thomas Petazzoni
2014-06-29 10:05 ` Arnout Vandecappelle
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=53AA66F5.3090706@mind.be \
--to=arnout@mind.be \
--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 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.