[Buildroot] [PATCH v2 1/5] kconfig-package: add support for config fragments

[Floris Bos <bos@je-eigen-domein.nl>]

On 05/02/2015 12:37 PM, Arnout Vandecappelle wrote:
> On 28/04/15 16:34, Floris Bos wrote:
>> Adds functionality to the kconfig infrastructure to merge additional
>> configuration fragment files to the main configuration file of
>> kconfig packages, using support/kconfig/merge_config.sh
>>
>> Typical use-case is when you want your configuration to be
>> kept in sync with an upstream (def)config file, but do require
>> some minor local modifications.
>>
>> Disables -update-config and -update-defconfig targets when
>> fragment files are set.
>>
>> Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
> [snip]
>
>> +* +FOO_KCONFIG_FRAGMENT_FILES+: a space-separated list of configuration
>> +  fragment files that are merged to the main configuration file.
>> +  Fragment files are typically used when there is a desire to stay in sync
>> +  with an upstream (def)config file, with some minor modifications.
>   I should have noticed this in the first iteration, but why do we need an
> additional config option for this? We could just rename _KCONFIG_FILE to
> _KCONFIG_FILES and update the help texts to explain that the files may consist
> of fragments.

Has been briefly discussed during the first iteration.
Main problem is _KCONFIG_FILE is not just a source file, but also a 
destination file for the update-config and update-defconfig targets.


-- 
Yours sincerely,

Floris Bos