User:Ronan
I'm more a Software architect. Sometimes it's hard to explain what you should do in the enterprise. I work on improve this state of thing.
Contents
- 1 OpenEmbedded Experience
- 2 Wishlist
- 2.1 better logs reports
- 2.2 bugzilla integration
- 2.3 reduce image size method
- 2.4 report tool
- 2.5 netboot images
- 2.6 some QA ideas
- 2.7 common & easy script encapsulation
- 2.8 OpenEmbedded showcase
- 2.9 target web interface
- 2.10 delivry/release class
- 2.11 emulator/qemu tasks
- 2.12 coreboot integration
- 2.13 Gentoo ebuild compatibility
- 2.14 use git facilities
- 3 Centers of interest related to openembedded
OpenEmbedded Experience
2006 - 2007 : Paper-book project
Prototype for paper-book
- http://scourge.fr/mathdesc/images/pb/PB-1.JPG
- http://scourge.fr/mathdesc/images/pb/PB-2.JPG
- http://scourge.fr/mathdesc/images/pb/PB-3.JPG
2007 - 2008 : Nao
Soon some information about it.
Wishlist
This section is my wiki for idea i'd like to work to improve my openembedded Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.
better logs reports
i missed important error compiling lost of software
bugzilla integration
if ( OE_WARN_BUG == 1 )
checkbug(${PN})
bitbake -bugz mozilla
cf http://code.google.com/p/pybugz/source/browse/trunk/README?r=28
reduce image size method
Reduce image size using remote lsof session on target to check useless files , packages ( blame useless dependency ) ... diff with $ROOTFS and eventually try them by size.
#REMOTE_METHODE = "ssh 192.168.0.1" REMOTE_METHODE = "tty /dev/USBtty1" bitbake -lsof-session mycustom-image.bb
http://www.ibm.com/developerworks/linux/library/l-inotify.html
i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ). Some Steiner stuff on fusil could be useful.
- /usr/include , /usr/share/, /usr/src ... .debug directory should be tested first.
report tool
print beautiful documentation on the distro/packages/whatever.
- template design
- baobab ...
netboot images
mkelf-linux kernel-image [ramdiskimage] keywords : initramdisk
some QA ideas
fuzzing our softwares
opkg, bitbake etc
- using fusil ( fuzzing report ) ,
i made the recipe see bug 4495 look success story at http://fusil.hachoir.org/trac/wiki/CrashList
more documentation
bbclass documentation ( how - as a policy ) => provide documentations about how to make better code in bitbake => pydoc , doctest , unittest , pyunit , pylint... byte compiling bbclass ? http://lists.idyll.org/listinfo/testing-in-python categories for /classes : qa,pkg,build,doc,...
test quality of a recipe : SRC_URI tarball contains no P/PV/PN => dangerous example "${NONFREE_MIRRORS}/oki/OKI_fse.tar.gz"
cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2
common & easy script encapsulation
OpenEmbedded showcase
some demonstration of OE ( video , screenshots ... ).
target web interface
- port Webif to OE
my bug report on this : WIP
- libopkg client support ( via http://packagekit.org/ ? )
- start a new one from scratch ? ( pylons based for example ).
delivry/release class
Produice a report on a delivry. Tool that give good report are often appricated ( there is something to show ). Managers/custumers/developers can keep useful and pretty trace of the project.
- log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -> rev-history , delivry-info )
- show software update
- show infos on bugs ( closed/news etc ) as a changelog
- show stats about image and packets ( boabab etc )
- show copyrights , licences ...
emulator/qemu tasks
some tasks that could be used for tests and debug.
- image is bootable ? ( ca be call in testsuite of task that build the img )
- test first boot
- upgrade not failed ? ( print the guilty )
- broken linkage ? ( can be call in testsuite of sanity.bbclass )
provides some methods
- build image
- launch with adapted parameter according to a qemu-machine conf
- NFS etc
see poky anjuta plugin and poky qemu scripts.
coreboot integration
- some recipes for utils
- use openembedded instead of buildrom ( yes another build system :/ )
Gentoo ebuild compatibility
using script ( crazy ) or common variables ( completely crazy ).
use git facilities
locate bug when upgrading oe
something like :
git bisect start git bisect bad ops = rec_ops(BB_CMD) if [ $? -eq 0 ] git bisect bad undo_ops(ops) else git bisect good fi
- if bug is a non-version fixed package , fix version and continue
- make a report
- cf http://www.miximum.fr/methodes-et-outils/79-debusquer-une-regression-avec-git-bisect ( fr )
- Industrial applications ( automation , robotic )
- Quality Assurance
- Gnome Mobile
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html
