[oe] [oe-commits] org.oe.dev SlugOS: ixp4xx-kernel - added 2.6.23.8 recipe and supporting files. (Note that

[Mike (mwester)]

Koen Kooi writes:
> mwester commit schreef:
> > SlugOS: ixp4xx-kernel - added 2.6.23.8 recipe and supporting files.
(Note that
> > SlugOS still selects 2.6.21 as the preferred version for now.)
>
> Why am I forced to download a 40MB 2.6.23.8 tarball instead of the small
> 2.6.23.8 patch? I already have 2.6.23 in DL_DIR.

The set of developers that will actually be using that recipe is
extraordinarily small (two at present), so the relative benefit of such
significant modifications to a stable, working bb skeleton just don't seem
worth the risk of breaking things for every user of the ixp4xx-kernel*.bb
recipes at the moment.  Yes, I agree that in a perfect world, fixing this
would be the Right Thing To Do(tm).

> It's as easy as doing:
>
> VANILLA_VERSION = "2.6.23"
> KERNEL_VERSION = "2.6.23.8"
>
>
> SRC_URI = "
> ${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${VANILLA_VERSION}.tar.bz2
> \
>
${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/patch-${KERNEL_VERSION}.bz2;patch=
1
> \
> "

I don't think so, in this case.  There's a lot of other logic in the include
file that looks like it will get in the way of this simple change.  I'll
look at it and see how it might be altered to handle this use-case (I don't
see that it currently does, although it seems to handle other kernel
patchsets nicely).  Just don't expect it to be fixed right away; there are
bigger problems right now with 2.6.23 and ixp4xx than the bb recipe (which
is why that recipe is not selected by default).

> in the recipe. I would have fixed it myself, but the huge block of
> python magic in ixp4xx-kernel.inc scared me away.

Perhaps this will force me to learn python.  Yes, I know it's not difficult,
but my brain crawls into the back of my head and protests mightily when it
is forced to use a language that reminds it so much of Fortran and the
horrors of column-sensitivity.  :p

Mike (mwester)