[Buildroot] [PATCH 0 of 5 RFC] uclibc/busybox: fix handling of configuration file

[Thomas De Schampheleire]

Hi Arnout,

On Wed, Jun 25, 2014 at 8:06 AM, Arnout Vandecappelle <arnout at mind.be> wrote:
>  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.

And additionally:

- 'make clean foo-update-config' should copy the initial file, do any
fixups, and then save the config

>
>  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))
>
>

This sounds like a very interesting idea, I'll explore it further in
the context of this patch series.

Best regards,
Thomas