Op 25 nov. 2011, om 12:44 heeft Paul Eggleton het volgende geschreven:

> Hi Koen / Beth / all,
> 
> Following on from my work extending packagehistory (which is still under 
> review), I'm looking at tracking history of the content of images so we can 
> get warnings about regressions. Thanks to Koen we've had this capability via 
> testlab.bbclass in OE for some time now, and from there into meta-oe, but 
> what 
> I'd like to do now is bring this into OE-core and extend it so that it 
> supports rpm (or even better, all of the package backends we support.) This 
> could involve abstracting the package backend functionality out into 
> rootfs_*.bbclass.
> 
> It also looks like testlab.bbclass in meta-oe has some license dumping 
> functionality. Beth, does that mesh with what you've been working on / 
> preparing for Yocto 1.2?
> 
> Thoughts?

Don't forget its integration into remote git: 
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/testlab/?h=yocto 
I must admit that it completely sucks when you have >1 builder, but that is 
fixable. There are a number of other things we need to store somewhere (e.g. 
package history, PR config, etc), so coming up with a plan to store all that in 
a single repo would be good.

The are a few issues with its current output:

* License info uses the filename instead of the package name 
(f'oo_1.2.3_arch.ipk' vs 'foo') which leads to too much changes with small 
version bumps
* Dependencies are not sorted intelligently, so sometimes you get diffs which 
don't contain any actual change, just ordering junk,
* It only reports oe-core rev, not layer revisions, config and shortlog. 
Ideally it would output something like:

meta: angstrom-staging:b3ffd40a4a1eacab90dac26df8a4a047486f3b96 pulseaudio: 
update to 1.1, delete 0.9.x
meta-oe: master:7019fbb50796fedcedef6ff92981a7f26659a251 mplayer: fix build 
with -Wl,-as-needed 
meta-efl:
meta-gnome:
meta-xfce:
meta-angstrom master:bc72e71ccf7e79cdc8246e0ae0dbe62d11355263 
angstrom-2010-preferred-versions.inc : Stop pinning python-cairo

Taking this a step further: it's output should be able to get passed into layer 
tooling (combo-layer to yocto people, setup-scripts for angstrom people) to 
reproduce builds.

regards,

Koen

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to