[Buildroot] Fwd: [PATCH 1/1] ola: new package

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

Dear David Skok,

On Thu, 15 Aug 2013 10:30:12 -0400, David Skok wrote:

> I checked with maintainer and karate and spi plugins build by mistake even
> with --disable to configure.  Will have to either live with that or take
> selection out and user assumes that it will be built.

Ok, then for now, remove the options for those plugins that are always
built, and only add options for plugins that can actually be
disabled/enabled.

>  The milinst plugin
> is new and I added it to the list as well as ordered all alphabetically.
>  Also found error with a plug in requiring python dependency in original
> patch and added python binding dependency comment for said plugin.
> 
> A general buildroot question...
> When plugin selections added after first build, ./configure is not re-run.
>  As such dependencies are built but not new plugins.  Is there something I
> need to put in package patch to make this work?

No, because we don't try to make this work. When an user changes the
Buildroot configuration, he has either to rebuild everything, or to
know what are the impacts of the configuration change and rebuild the
corresponding packages.

The problem is that it is almost impossible to know what is the impact
of an arbitrary change in the configuration, so we don't try to handle
this, it's part of the KISS principle.

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