followup of a post from a while back, here's a snippet from core-image.bbclass:
=== CORE_IMAGE_BASE_INSTALL = '\ task-core-boot \ task-base-extended \ \ ${CORE_IMAGE_EXTRA_INSTALL} \ ' CORE_IMAGE_EXTRA_INSTALL ?= "" IMAGE_INSTALL ?= "${CORE_IMAGE_BASE_INSTALL}" === then there's this from core-image-gtk-directfb.bb: === inherit core-image IMAGE_INSTALL += "\ ${CORE_IMAGE_BASE_INSTALL} \ task-core-basic \ task-core-gtk-directfb-base \ " === argh. as i read it (and i don't trust myself to read any of this properly anymore), appending ${CORE_IMAGE_BASE_INSTALL} is superfluous since it's already there from core-image.bbclass. and, again, what's best practice for appending to IMAGE_INSTALL? +=? _append? just trying to mentally enforce some order on all of this. rday p.s. and as i muttered about before, this sort of thing from core-image-clutter.bb: === IMAGE_INSTALL = "\ ${CORE_IMAGE_BASE_INSTALL} \ task-core-clutter-core \ task-core-clutter-tests \ task-core-clutter-apps" inherit core-image === really just introduces unnecessary confusion, as CORE_IMAGE_EXTRA_INSTALL would have been the obvious thing to use here, no? -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core