From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Philip Balister <philip@balister.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] psplash fixes
Date: Wed, 21 Dec 2011 15:15:19 +0000 [thread overview]
Message-ID: <2148975.ysQ11QrYeT@helios> (raw)
In-Reply-To: <4EF0AA68.7070501@balister.org>
On Tuesday 20 December 2011 10:31:52 Philip Balister wrote:
> 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.
I'm not entirely convinced this workflow makes sense when you're interested in
getting reproducible product images. This is basically the "take some existing
distro and hack it up until it fits" approach which taken past a certain point
leads to an unmaintainable mess, or at the very least regressions.
People really ought to be able to produce their final images from the metadata
with no additional post-build changes (or at least none that are manual). If
that's too difficult, that's the problem I think is most worthwhile to attack,
even if it requires more work on our part.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-21 15:22 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
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 [this message]
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=2148975.ysQ11QrYeT@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philip@balister.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox