From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <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:57 +0000 [thread overview]
Message-ID: <3289178.cJ7bor4PPM@helios> (raw)
In-Reply-To: <756581D3-FAA6-48FC-9ECE-0B7CC1262A5D@dominion.thruhere.net>
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?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-19 19:04 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
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 [this message]
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=3289178.cJ7bor4PPM@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.