[Buildroot] [PATCH 13/14] enable config.cache per default

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Le Wed, 07 Oct 2009 22:59:37 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

>  Bernhard>   It speeds up configuration considerably.
>  Bernhard>   If a package breaks due to wrong cache-entries, then the
>  Bernhard> broken other package has to be fixed, not the innocent
>  Bernhard> bystander!
> 
>  Bernhard>   Put short: There is absolutely _no_ need to ever turn
>  Bernhard> the cache off unless you hack on autotools itself and goof.
> 
> In that case, why do we even have the config option?

Originally, because when the change was introduced, some packages were
failing due to incorrect dependencies. And the contributor didn't want
to break many packages at once and preferred to have a intermediate
step where this is an option.

I think we can now get rid of the option. Or introduce some kind of
?Buildroot Hacking? menu/submenu where we put this kind of very
advanced options that normal users shouldn't use, but that can be
helpful for debugging. And when doing support, we could also ask users
to enable the option that disables the cache to see if it fixes a
reported failure.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com