Hi, I've talked to someone on FOSDEM about OE, and wanted to try it (I also just started to use OpenWrt for a university project)
These are my first time user notes (and suggestion for improvements). Starting with: http://www.openembedded.org/wiki/Main_Page and especially the "Getting Started" Page. This seems to be outdated (using the classic repos and not the "layered" core. Building the classic branch did not work out for me. Not a very good first user experience. I suggest that the the Getting Started page is replaced with the contents from wiki.yoctoproject.org/wiki/OpenEmbedded-Core (and slighly enhanced). Building the -core was also problematic. Two packages caused troubles: zlib and another package (don't know the name anymore). Both problems were caused because it could not download some files. It seems zlib.org removed all downloads prior to 1.2.6, and OE uses 1.2.5. Applying the patch from http://patches.openembedded.org/patch/20641/ fixed the problem. The other package could not be downloaded because it was hosted on kernel.org and the content seemed to have been removed. http://permalink.gmane.org/gmane.comp.handhelds.openembedded.core/14810helped me fix the issue. Suggestion 2: These download problems seems not be fixed very rapidly (although they should be quite easy to fix). I wonder why. My theory (but prove me wrong), is that developers won't see this because they have the download cached in their download directory So only new users will discover this. One solution could be to have a dedicated "test" machine that tries to download every package every day (or at least see if it still exists). Once a failure happens it is reported to a log/bug system. In the case of zlib: if they remove the previous version every time when releasing a new one it should be better to mirror the files on your own hosts, otherwise every time zlib does a release OE won't work for some time. Suggestion 3: Create a site like " https://community.dev.fedoraproject.org/packages/"; where one can search for packages / recipes. This site should integrate with * Recipe info (name, maintainer, layer, version info, changelog info, ...) * Bugs * Incomping Patches / reviews * Build results For build results: (which is suggestion 4): Create dedicated server machines that test each and every package every time it is updated (built without any other packages except for its dependencies, with several toolchain configurations - combinations of target / libc implemenation / gcc version / ...). In the optimal case every package should be tested with every possible combination of enabled features but that is probably not possible. This way errors will be quickly detected. I already have to apologize: it seems that these already exists (somewhat), in the form of tinderbox.openembedded.net and garnet.openembedded.org (I've found about them when looking on the Infrastructure Wiki page), but they don't load here... (Are they still maintained / what are they doing exactly?) Greetings, Nathan Samson _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
