Re: [RFC] Rebuild external kernel modules on kernel change

[Koen Kooi <k.kooi@student.utwente.nl>]

On 04-04-09 22:18, Frans Meulenbroeks wrote:
> 2009/4/4 Koen Kooi<k.kooi@student.utwente.nl>:
>> On 04-04-09 17:51, Frans Meulenbroeks wrote:
>>>
>>> Hm,
>>>
>>> I don't like that one needs to touch conf/machine/beagleboard.conf
>>> each time the kernel is updated.
>>> This is likely to be forgotten at some time.
>>> Can't we use something in the linux-omap-*.bb file ?
>>
>> You can't set global vars in recipes.
>
> Thinking of it the real issue is that we do have DEPENDS that takes
> care that if A needs B, B is build before A (and I guess that after
> updating B a bitbake of A will result in a recompile, even if A's PR
> is not changed.
>
> Maybe a solution could be to be able to rebuild a package plus all its
> dependencies (the information is there in the DEPENDS lines).

We can already do that with BB_STAMP_POLICY, the problem present is that 
it will generate packages with the same PV and PR, so it won't show up 
as upgrade, so users get a broken installation after the package manager 
upgrades the kernel, but not the modules since PV and PR didn't change 
for those.

regards,

Koen