For a long time we've talked about what to do with BOOTSTRAP_EXTRA_RDEPENDS as whilst is does what some people need, it doesn't cover every users needs and the machine conf files are starting to contain information that should be under distro control.
I've been attempting to find a way forward and have just added something to poky which I think would be an improvement on the situation in OE: http://svn.o-hand.com/view/poky/trunk/meta/packages/tasks/task-base.bb?rev=562&view=auto The idea is machines state which features they have e.g.: MACHINE_FEATURES_spitz = "kernel26 apm alsa pcmcia bluetooth irda usbgadget usbhost ext2" and distributions set which items they'd like to appear in their standard images e.g.: DISTRO_FEATURES = "alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi" and the task file combines these variables and comes up with a machine specific task package suited to the machine and distribution. So variables are by machine selection, some by distro selection and some are controlled by both. task-base-oh-minimal is an example of how we can have several forms of this task to suit different needs e.g. maybe one suited for initrds. This solution was based on the module lists used by the Zaurii and ipaqs in OE so should be capable of covering at least those machines once the tosort list is dealt with. There are a couple of functions that need to be added to base.bbclass to make it work. Does anyone have any thoughts on this? I'd be interested if anyone could give examples of the types of images they'd like to generate from OE. task-bootstrap is one but what should an initrd contain for example? Richard _______________________________________________ Oe mailing list [email protected] https://www.handhelds.org/mailman/listinfo/oe
