[Buildroot] [PATCH 2 of 9 v4] Config.in.legacy: update description for users
Arnout Vandecappelle
arnout at mind.be
Tue Sep 3 16:50:47 UTC 2013
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.
Regards,
Arnout
--
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
More information about the buildroot
mailing list