From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-architecture@lists.openembedded.org,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: Split do_rootfs into image specific tasks?
Date: Wed, 06 Jan 2016 23:04:53 +0000 [thread overview]
Message-ID: <1452121493.7598.101.camel@linuxfoundation.org> (raw)
In-Reply-To: <3002291.NNtibCZEiD@peggleto-mobl.ger.corp.intel.com>
On Wed, 2016-01-06 at 10:30 +1300, Paul Eggleton wrote:
> I like this a lot. I'd idly considered this model before (as I'm sure
> others
> had) as it simplifies a lot of the multi-format image construction
> handling,
> improves incremental performance, and the added granularity makes it
> slightly
> easier to see what the build system is doing. Obviously there is some
> minor
> cleanup work to be done on the patchset as you've noted.
>
> The only "issue" I can think of is that bitbake -c rootfs will no
> longer build
> the image files as it did previously; however I'm not sure I'd
> structure things
> any differently to avoid that though. I suspect people will fairly
> easily adapt
> to this change as long as we publicise it effectively.
Thanks for the feedback. Just as a heads up for people, I posted an
updated patch set to the OE-Core list. This one has various issues
fixed (including the todos) and is ready for wider testing.
Cheers,
Richard
prev parent reply other threads:[~2016-01-06 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 13:00 RFC: Split do_rootfs into image specific tasks? Richard Purdie
2015-12-28 13:18 ` [Openembedded-architecture] " Richard Purdie
2016-01-04 10:55 ` Patrick Ohly
2016-01-06 23:11 ` Richard Purdie
2016-01-05 21:30 ` Paul Eggleton
2016-01-06 23:04 ` Richard Purdie [this message]
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=1452121493.7598.101.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.