Re: Why does this have to be so ##@&$@$! difficult?
Sorry, I did try to give enough discussion in my last answer to illustrate the general approach, as well as the specific. To be completely general then:
a) check for the version you need in the chumby-oe tree. It
may be there, but not being pulled unless you explicitly change the version
in your image recipe.
b) check in the head of the openembedded repo and if it is there, copy it over along
with any support files. You may have to move more packages to resolve dependencies.
In an ideal world our OE tree would regularly merge in changes to the head, but the are changes in the head that
make the Chumby unbootable, and AFAIK no one has ever identified which
updates or why.
c) Search around for someone else's work that isn't in the openembedded master tree.
There are lots of people building OE recipes and posting them to various places.
d) Build it yourself. Start with the bb file you have, copy it,
start editing and testing. Sometimes this turns out to be trivial, sometimes very much non-trivial.
Yeah, it's hard. When we eventually get the 3.4 kernel and post-classic(?) OE booting on the Chumby this should be a lot easier because we will be operating with the current kernel and OE sources. But there is a lot of work to do to get there.