[Buildroot] [PATCH 2 of 9 v4] Config.in.legacy: update description for users

[Thomas De Schampheleire]

Hi Arnout,

On Tue, Sep 3, 2013 at 6:50 PM, Arnout Vandecappelle <arnout at mind.be> wrote:
> On 09/03/13 17:06, Peter Korsgaard wrote:
>>>>>>>
>>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
>>>>>>> writes:
>>
>>
>>
>>   Thomas> So far, the only problem I see with this are related to minimal
>>   Thomas> defconfigs. In the case (1) above, the minimal defconfig will
>> continue
>>   Thomas> to contain the name of the legacy option, and not the name of
>> the new
>>   Thomas> option, since the new option is selected by the legacy option.
>> This is
>>   Thomas> annoying since it means minimal defconfigs are not progressively
>>   Thomas> updated to use the new option name. And this probably makes my
>> entire
>>   Thomas> proposal moot.
>>
>> Damn, yes :/
>>
>> So people really do need to explictly change to the new option / restart
>> make menuconfig.
>
>
>  I never tried it, but a workaround could be to run olddefconfig before any
> interactive config (menuconfig, nconfig, xconfig, qconfig). olddefconfig
> should be equivalent to saving immediately.

I tried it manually (not yet integrated in a Makefile) and it works as expected.
However, a disadvantage is that any new symbol will no longer be
marked as NEW in the interactive config. So the trade-off would be
between loosing this NEW marker, and requiring the user to do an
intermediate save.

Best regards,
Thomas