Structure of .dev branch

From Openembedded.org

In keeping with the Commit Policy we'd like to make it clearer what the different areas of the metadata are. Currently having everything under packages/ is a bit overwhelming.

A structure similar to the one below is proposed:

classes/* as existing
conf/* as existing
packages-core/
packages-gpe/
packages-openmoko/
packages-opie/
packages-qt/
packages-sdl/
packages-toolchain/
packages-x11/
packages/

"packages-toolchain/" would be the toolchains (binutils, gcc, libtool, automake, autoconf, pkgconfig, glibc, uclibc etc.) and would be the core toolchain components.

"packages-core/" would contain some *basic* tasks and images so on top of packages-toolchain this would mean busybox, tinylogin, sysvinit, etc. with the components here being those required to make the small/minimal images.

"packages-gpe" and friends are self explanatory, the main reason for them would be to cut down on parsing time for those not building gpe/opie/sdl/x11/openmoko/whatever. Anything which we can cleanly split off could go here.

"packages" would contain anything that doesn't fit the other categories.

Its proposed we do it gradually and as we do it, clean up the recipes and start automated testing of categories so we know what builds. My initial proposal would be to use qemuarm/qemux86 and add other qemu machines for the other architectures as we go. People wanting to test specific machines would also then be free to do so.