[oe] Merging openmoko into OE
laforge at openmoko.org
Mon Mar 5 17:12:59 CET 2007
On Mon, Mar 05, 2007 at 03:46:35PM +0000, Richard Purdie wrote:
> Mickey mentioned something very briefly about a problem but he was in a
> hurry and I'd actually misunderstood the problem looking at this :/. I
> also thought he'd found a solution that worked for now meaning more time
> could be spent solving it properly.
the interim solution was to rebuild everything all the time (srcdate in
PR), but that's no longer acceptable now.
> In future, please do send a mail to the bitbake development list if
> there are problems like this.
> Even if you don't switch to using 1.8.x, it would be good if you did
> have time to test it and let us known what (if any :) issues you have
> with it. I'm about to send something to the lists requesting testing
> before we release 1.8.0.
i'll see if I can find somebody 'qualified' to do that :)
> > > > Holger and I discussed something like that for the packaged-staging project, but we didn't
> > > > come up with a clean way to present it to the user. That was last year, and I'm sure
> > > > others can come up with something.
> > >
> > > This needs packaged staging which is quite an effort. Please do discuss
> > > this before implementation as we've tried things before and know roughly
> > > how this can work.
> > ok, will do. this is less important at the moment.
> This is a long term project aim for OpenEmbedded (and me personally)
> since it doesn't just solve this problem but solves a number of others
> too. It would be great to see it developed.
well, what I actaully would love to see is native host distro rpm/dpkg
file creation for at least the toolchain, but in the end acutally also
the staging, yes.
Another issue that we're running into is this inevitable
rebuild-everything-from-scratch when you just want to temporarily test
something. There should be an easy way to keep all native packages,
toolchain, etc. and only rebuild everything for the target, i.e. start
again with bootloader/kernel/glibc/... for arm in our case.
> > If there are existing plans/ideas in this area, or somebody with some
> > ipkg background has a good proposal and wants to implement it as paid
> > contractor, this would be the time to talk about it.
> I think lots of people, me included have looked at the ipkg code and
> wanted to see it rewritten with something like a sqlite backend rather
> than parsing its ascii files all the time.
So did anyone make actual plans on how to go about this?
Or alternatively: Is there somebody who would be available on short
notice and interested in implementign such a backend as a paid contract
job? Please step up now :)
- Harald Welte <laforge at openmoko.org> http://openmoko.org/
Software for the world's first truly open Free Software mobile phone
More information about the Openembedded-devel