[oe] [PATCH] package_ipk.bbclass DON'T PUSH THIS, but PLEASE read it

[Richard Purdie]

On Wed, 2010-03-03 at 13:54 +0100, Martin Jansa wrote:
> On Fri, Feb 26, 2010 at 10:15 PM, Martin Jansa <martin.jansa at gmail.com> wrote:
> > There is quite common error about non-existent lockfile path
> >
> > I've seen that everytime when recipe changes ARCH (ie when removed machine specific config)
> > and package is no longer in tmp/work/om-gta01.. but tmp/work/armv4t.., then whole build works
> > ok, but in the end it's looking for lockfile in right directory but in wrong arch dir.
> >
> > Today I've seen similar error from mwester:
> > 18:10:59 < mwester> ERROR: Error, lockfile path does not exist!: /u/slug/slugos/tmp/work/armv5teb-linux-gnueabi/gpsd-2.39-r0/packages-split
> 
> ping?
> 
> I think this is quite big bug as wrong vars can be used in more places
> and create bigger problems than missing lockfile path.
> 
> At least please point me to example why we need collapsed subpackage
> data in global scope.
> 
> RP: sorry for adding you to CC directly, but you would probably know,
> if the variable name collapsing fuction from Poky:
> http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=634c76d02e5796f5e908b6d6a79dcfef6f8af3d1
> should be somewhere in this code path.

Its a serious bug I agree but a very hard one to fix. The correct fix is
to have staging under full control of a packaging system, then when you
clean packages, all the right bits are actually removed.

In that sense this is no better or worse than the other 101 ways you can
break staging.

So in summary, no easy fix, we need to fix the big general problem -
packaged staging needs to be on by default and used by everything. Only
then will we nail all these problems.

Cheers,

Richard