On Monday 19 December 2011 19:27:06 Koen Kooi wrote: > Op 19 dec. 2011, om 19:22 heeft Paul Eggleton het volgende geschreven: > > On Monday 19 December 2011 18:50:35 Koen Kooi wrote: > >> Op 19 dec. 2011, om 18:43 heeft Paul Eggleton het volgende geschreven: > >>> Set the default psplash image to the OpenEmbedded logo, and provide > >>> a > >>> script to allow people to use their own custom image. > >> > >> What I did in OE-classic and meta-angstrom is to use > >> update-alternatives to provide different psplash images. This way you > >> can choose a different splash for each image instead of having a > >> distro wide one. Is something like that suitable for oe-core as well? > > > > Sounds like a useful capability, however, does this mean that when you > > want to override it in the image you end up with both psplash versions > > installed? > in a splashless image you can just do 'IMAGE_INSTALL += psplash-angstrom and > it will only install that one. If you want to reuse an existing, unmodified > image with psplash and add your own, then you will end up with both.
Although I guess another way to do it would be to do a VIRTUAL-RUNTIME type thing like we do for other such selections. At the moment in OE-core, psplash is brought in via task-core-console, and whilst it is a separate variable that could be overridden it's a task which once built really makes it impossible to customise per-image. What about a "splash" IMAGE_FEATURE and then a VIRTUAL-RUNTIME_splash to select which psplash to install? Would update-alternatives be needed at all in that case? 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
