On 12/19/2011 01:57 PM, Paul Eggleton wrote: > On Monday 19 December 2011 19:48:48 Koen Kooi wrote: >> I will say again: I absolutely HATE that virtual-runtime nonsense. If you >> need to change a task, change the task, don't introduce things that make it >> non deterministic. Guess what happens when you change a virtual-runtime >> *after* you have built the task already. > > This is the problem I'm trying to avoid. Perhaps it wasn't clear, but what I > meant was change things so we do not bring in psplash via a task anymore - > instead use the value of VIRTUAL-RUNTIME_splash within core-image.bbclass, > controlled via an IMAGE_FEATURE. > >>> Would update-alternatives be needed at all in >>> that case? >> >> It would if you want to change it after booting :) > > What's the use case for changing the splash image after booting?
I can see people taking an existing image, adding a few packages to customize it for their application, and changing the splash image to a product specific one. Philip _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
