From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: koen@dominion.thruhere.net
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] psplash fixes
Date: Mon, 19 Dec 2011 18:22:18 +0000 [thread overview]
Message-ID: <1817157.LPoMfdErnK@helios> (raw)
In-Reply-To: <D88949C2-F8C7-4CAF-B74C-32AE43119D20@dominion.thruhere.net>
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?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-19 18:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 17:43 [PATCH 0/2] psplash fixes Paul Eggleton
2011-12-19 17:43 ` [PATCH 1/2] psplash: use OpenEmbedded logo Paul Eggleton
2011-12-20 9:55 ` Paul Menzel
2011-12-19 17:43 ` [PATCH 2/2] scripts/contrib: add a script to create a psplash image header Paul Eggleton
2011-12-19 17:50 ` [PATCH 0/2] psplash fixes Koen Kooi
2011-12-19 18:22 ` Paul Eggleton [this message]
2011-12-19 18:27 ` Koen Kooi
2011-12-19 18:32 ` Paul Eggleton
2011-12-19 18:48 ` Koen Kooi
2011-12-19 18:57 ` Paul Eggleton
2011-12-19 19:02 ` Koen Kooi
2011-12-19 19:12 ` Paul Eggleton
2011-12-21 15:16 ` Paul Eggleton
2011-12-20 15:31 ` Philip Balister
2011-12-21 15:15 ` Paul Eggleton
2011-12-23 0:00 ` Philip Balister
2011-12-20 7:33 ` Martin Jansa
2011-12-21 15:40 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1817157.LPoMfdErnK@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.