[poky] [PATCH] Update poky-feed-config-opkg to generate a useful package setup

[Richard Purdie]

On Fri, 2011-09-02 at 11:10 -0600, Gary Thomas wrote:
> On 2011-09-02 11:04, Richard Purdie wrote:
> > On Fri, 2011-09-02 at 10:46 -0600, Gary Thomas wrote:
> >> The current poky-feed-config-opkg package only generates a skeleton for the
> >> opkg setups.  In particular, the base configuration file /etc/opkg/base-files.conf
> >> is not filled in at all.
> >>
> >> The attached patch fills this file in, using variables set by the
> >> user (local.conf, site.conf, etc).  If left unset, the behaviour will
> >> be the same as current.
> >>
> >> One thing I found is that opkg is very noisy if there are databases
> >> mentioned in base-files.conf that don't exist.  For example, on ARM
> >> platforms, there are a large number of possibilities (arm, armv5, armv6, ...)
> >> that are never populated in .../tmp/deploy/ipk.  The changes to this
> >> recipe will prune the file to only include those ipk databases which
> >> have actual files present.
> >
> > Your code is one big race unfortunately since the actual file generated
> > will depend on whether any packaging task has run before it or not (and
> > what package type that was). I'm not sure how to fix that but it can't
> > go in as it stands due to that...
> 
> I agree :-)  That's what these lines are for:
>    do_compile[depends] += "base-files:do_package"
>    do_compile[depends] += "virtual/kernel:do_package"
> 
> They solve the problem for me, i.e. if I build an image which includes
> this recipe from scratch, then the do_compile step is held off until
> sufficient work has gone on to make the database useful.

Sorry, I didn't see that on the bottom. I can't say I really like it. If
you're going to do that you might as well just hardcode the list as:

"all ${TUNE_PKGARCH} ${MACHINE}"

?

Cheers,

Richard