On Wednesday 15 August 2012 12:54:17 Koen Kooi wrote: > Op 15 aug. 2012, om 11:46 heeft Paul Eggleton <paul.eggle...@linux.intel.com> het volgende geschreven: > > 2) Look at the existing tasks and: > > * evaluate their usefulness > > * remove any that are obsolete > > * adjust existing contents if needed > > * look for useful groups of packages that might be added > > > > We need to pay particular attention to task-core-boot and task-base as > > these are pulled in by default in any image that inherits from > > core-image.bbclass - if these are not generally working for people that > > are creating their own images, we need to change them such that they are. > > Have a look at task-boot and task-basic in meta-oe: > https://github.com/openembedded/meta-oe/tree/master/meta-oe/recipes-core/ta > sks
OK, I've taken the opportunity to summarise the tasks in meta-oe on the following page: http://www.openembedded.org/wiki/Meta-oe_tasks meta-oe's task-basic indeed contains much less than task-base; it provides an alternative (and possibly simpler) means of selecting between ssh or dropbear, although it prevents it being an image-level decision if that's something people care about. I'm not convinced it's appropriate to unconditionally install avahi, htop and cpufrequtils though - those look distro-specific to me. For meta-oe's task-boot, it doesn't seem all that different from task-core-boot with the exception that task-core-boot imposes modutils-initscripts (should probably be fixed), and that task-boot mandates that the kernel be installed which is not always needed depending on how the bootloader works on whatever machine is being built for - although kernel.bbclass seems to indicate that currently the machine is supposed to influence this by setting RDEPENDS_kernel- base which seems a little backwards to me. I'd like to hear from other users of these tasks (Martin?) > My pet peeve is the bloat oe-core forces onto qemu* builds in the name of > "our testing team needs it!!!". Why am I forced to build an nfs server and > distcc when setting MACHINE=qemusomething? If you're referring to qemu-config (which depends on distcc, task-core-nfs- server, oprofileui-server, rsync and bash) it's important to note that it only gets enabled for qemu* machines by the poky distro config via POKYQEMUDEPS, so this is not being used by OE-Core - in fact nothing in OE-Core refers to qemu- config at all. I still have an open bug to fix this (#1690), and I agree it's egregious, but it's a Poky issue, not an OE-Core one. For the record, the reason for including them is not "our testing team needs it!!!" - it was the assumption made a long time ago that these things would be generally useful for development on emulated targets. Whether or not that assumption is still correct is another issue. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
