[Angstrom-devel] Kernel modules build/install issues, was: Re: Fwd: ipaq h4100 bluetooth and wifi issues

[Richard Purdie]

On Tue, 2007-09-11 at 13:32 +0300, Paul Sokolovsky wrote:
> So, on each kernel recipe rebuild (and only then), one needs to
> manually remove (or move to morgue dir to be more correct) all
> previous kernel module packages:
> 
> rm tmp/deploy/glibc/ipk/h4000/kernel-module-*
> 
>   Again, this should happen only if kernel is to be rebuilt, not
> unconditionally before any image rebuild.
> 
> > ipaq - h4100
> > version - Linux version 2.6.21-hh12 (koen at bitbake) (gcc version 4.1.2) #1
> > PREEMPT Tue Aug 28 02:58:07 CEST 2007
> 
>   And this means that this issue happens on official Angstrom build
> server too, with noone to do cleanups manually, of course. Koen,
> Richard, any ideas how to automate it? Do we speak about adding a
> pre-package task which would fish in deploy dir? Would this be ok?
> (But hardly any other choice of course.)

This is part of a bigger problem in OE which is that the deploy
directory can easily become corrupted. Say package foo has:

PACKAGES += "foo-extras1 foo-extras2"

and then you change it to:

PACKAGES += "foo-extras3"

tmp/deploy/ipk will still have foo-extras1 and foo-extras2 in it. Thats
a similar bug.

Another example: "bitbake foo-2.0" then "bitbake foo-1.0"

foo 1.0 ends up in the morgue, 2.0 in deploy. Again, a similar related
bug.


The ultimate solution is actually a form of packaged staging. I would
argue deploy should be under control of a package manager as well as
staging so package X can be uninstalled and replaced by the new version.

Rather than hacking specific cases like kernel modules I would like to
see the root problem addressed in a generic fashion...

Cheers,

Richard