https://www.openembedded.org/api.php?action=feedcontributions&user=Svererenov&feedformat=atomOpenembedded.org - User contributions [en]2024-03-19T13:49:24ZUser contributionsMediaWiki 1.29.0https://www.openembedded.org/index.php?title=User:Ronan&diff=5421User:Ronan2012-12-10T19:09:38Z<p>Svererenov: </p>
<hr />
<div>I'm more a [http://en.wikipedia.org/wiki/Software_architect Software architect].<br />
Sometimes it's hard to explain what you should do in the enterprise. I work on improve this state of thing.<br />
<br />
= OpenEmbedded Experience =<br />
<br />
== 2006 - 2007 : Paper-book project ==<br />
<br />
Prototype for [http://www.paper-book.com paper-book]<br />
<br />
* http://scourge.fr/mathdesc/images/pb/PB-1.JPG<br />
* http://scourge.fr/mathdesc/images/pb/PB-2.JPG<br />
* http://scourge.fr/mathdesc/images/pb/PB-3.JPG<br />
<br />
== 2007 - 2008 : Nao ==<br />
<br />
Soon some information about it.<br />
<br />
= Wishlist =<br />
<br />
This section is my wiki for idea i'd like to work to improve my openembedded <br />
Some are perhaps really bad ideas ( not enough searsh ), or already exists , let me know.<br />
<br />
== better logs reports ==<br />
<br />
i missed important error compiling lost of software<br />
* http://opensource.bolloretelecom.eu/projects/oestats/wiki/oestats<br />
* should we use logging python module ?<br />
<br />
== bugzilla integration ==<br />
<br />
if ( OE_WARN_BUG == 1 )<br />
checkbug(${PN})<br />
<br />
bitbake -bugz mozilla <br />
<br />
cf :<br />
* seppuku.bbclass<br />
* http://code.google.com/p/pybugz/source/browse/trunk/README?r=28<br />
<br />
== reduce image size method ==<br />
<br />
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.<br />
<br />
#REMOTE_METHODE = "ssh 192.168.0.1"<br />
REMOTE_METHODE = "tty /dev/USBtty1"<br />
bitbake -lsof-session mycustom-image.bb<br />
<br />
http://www.ibm.com/developerworks/linux/library/l-inotify.html<br />
<br />
i should also try some code inspector ( to check code duplication etc to advise programmer where place could be saved ).<br />
Some Steiner stuff on fusil could be useful.<br />
<br />
* /usr/include , /usr/share/, /usr/src ... .debug directory should be tested first.<br />
<br />
== report tool ==<br />
<br />
print beautiful documentation on the distro/packages/whatever.<br />
* template design<br />
* baobab ...<br />
<br />
perharps [http://www.reportlab.org/rl_toolkit.html reportlab] APPS for oestats. Look http://docs.djangoproject.com/en/dev/howto/outputting-pdf/ ( example works pretty well).<br />
<br />
== netboot images ==<br />
<br />
mkelf-linux kernel-image [ramdiskimage]<br />
keywords : initramdisk <br />
<br />
== some QA ideas ==<br />
<br />
=== fuzzing our softwares ===<br />
<br />
opkg, bitbake etc<br />
<br />
* using [http://fusil.hachoir.org fusil] ( fuzzing report ) ,<br />
i made the recipe see [http://bugs.openembedded.net/show_bug.cgi?id=4495 bug 4495]<br />
look success story at http://fusil.hachoir.org/trac/wiki/CrashList<br />
<br />
=== more documentation ===<br />
<br />
==== bitbake documentation ====<br />
I started bitbake developer documentation here : [[Bitbake]]<br />
TODO :<br />
<br />
* provide documentations about how to make better code in bitbake<br />
* pydoc , doctest , unittest , pyunit , pylint...<br />
* byte compiling bbclass , what is done by cache ?<br />
* http://lists.idyll.org/listinfo/testing-in-python<br />
* categories for /classes : qa,pkg,build,doc,...<br />
<br />
==== bbclass documentation ====<br />
<br />
* should this features be implemented as a bbclass or in bitbake core library ? <br />
* authors and contact in bbclass ! some of its need to be rewrite due to changes in python => 2.4 , we should detects them<br />
and add to a TODO-featuring tracker.<br />
* force to provide documentation as a policy<br />
<br />
=== test quality of a recipe ===<br />
<br />
* (all ?) field well filled <br />
* SRC_URI tarball contains no P/PV/PN => dangerous<br />
* no SRCREV fixed , PV = "x.y.z+svnr${SRCREV}" : <br />
perharps allow in a pending branch and auto-apply in the stable one. <br />
http://projects.linuxtogo.org/pipermail/openembedded-devel/2007-July/002639.html<br />
* are SRC_URI fetchable ? we can fix it automagically changing SRC_URI for our MIRROR <br />
* initscript without INITSCRIPT mecanism ( we need , for each new mecanism, write a recipe test and documentation )<br />
* do_install with cp cmd instead of install <br />
* warns on RPROVIDES<br />
* recipe modification without upgrade the PR<br />
<br />
cf : http://handhelds.org/~zecke/bitbake-qa-0.1.tar.bz2<br />
<br />
== common & easy script encapsulation ==<br />
<br />
== OpenEmbedded showcase ==<br />
<br />
We should promote OE projects (not only fic & o-hand.com stuffs)<br />
<br />
== target web interface ==<br />
<br />
* port Webif to OE<br />
my bug report on this : WIP<br />
<br />
* libopkg client support ( via http://packagekit.org/ ? )<br />
* start a new one from scratch ? ( pylons based for example ).<br />
<br />
== delivery/release class ==<br />
<br />
Produce a report on a delivery.<br />
Tool that give good report are often appreciated ( there is something to show ).<br />
Managers/customers/developers can keep useful and pretty traces of their projects.<br />
<br />
* log/tag revision of each versioned tree ( that are not in distro/src-revs ) ( mtn status / svn info / -> rev-history , delivery-info )<br />
* show software update<br />
* show infos on bugs ( closed/news etc ) as a changelog<br />
* show stats about image and packets ( boabab etc )<br />
* show copyrights , licenses ...<br />
<br />
== emulator/qemu tasks ==<br />
<br />
some tasks that could be used for tests and debug.<br />
* image is bootable ? ( ca be call in testsuite of task that build the img )<br />
* test first boot<br />
* upgrade not failed ? ( print the guilty )<br />
* broken linkage ? ( can be call in testsuite of sanity.bbclass )<br />
<br />
provides some methods<br />
* build image<br />
* launch with adapted parameter according to a qemu-machine conf<br />
* NFS etc<br />
<br />
see poky anjuta plugin and poky qemu scripts.<br />
<br />
== coreboot integration ==<br />
<br />
* some recipes for utils <br />
* use openembedded instead of buildrom ( yes another build system :/ )<br />
<br />
== Gentoo ebuild compatibility ==<br />
<br />
using script ( crazy ) or common variables ( completely crazy ).<br />
<br />
== use git facilities ==<br />
<br />
=== locate bug when upgrading oe ===<br />
something like :<br />
<br />
git bisect start<br />
git bisect bad<br />
ops = rec_ops(BB_CMD)<br />
if [ $? -eq 0 ]<br />
git bisect bad<br />
undo_ops(ops)<br />
else <br />
git bisect good<br />
fi<br />
<br />
* if bug is a non-version fixed package , fix version and continue<br />
* make a report<br />
* cf http://www.miximum.fr/methodes-et-outils/79-debusquer-une-regression-avec-git-bisect ( fr )<br />
<br />
== IDE integration ==<br />
<br />
http://community.buglabs.net/kgilmer/posts/3-OpenEmbedded-Tools-for-Eclipse<br />
<br />
= Centers of interest related to openembedded =<br />
<br />
* Industrial applications ( automation , robotic ) see http://objects.reprap.org/wiki/User:Ronan<br />
* [[Quality Assurance]]<br />
* [http://www.gnome.org/press/releases/gmae.html Gnome Mobile]<br />
* [http://www.rushessay.com/prices.php buy essay]<br />
<br />
http://zecke.blogspot.com/2006/10/softwareengineering-and-qa-for-free.html http://projects.linuxtogo.org/pipermail/openembedded-devel/2006-September/000323.html<br />
<br />
<br />
<br />
<br />
Oh! That's great! Thank you for post! Awesome!And one more thing:If you will have some free time, you can find many goods for yourself here - That's just about [http://customessayorder.com/custom-essay.php essay writing services]</div>Svererenov