From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 05/10] swupdbundle: new class to generate virtual images for swupd-image
Date: Tue, 01 Mar 2016 13:45:44 +0000 [thread overview]
Message-ID: <1456839944.3290.3.camel@linux.intel.com> (raw)
In-Reply-To: <1456419979.30039.67.camel@intel.com>
Hi Patrick,
Apologies for the delayed response.
On Thu, 2016-02-25 at 18:06 +0100, Patrick Ohly wrote:
> On Wed, 2016-02-24 at 14:52 +0000, Joshua Lock wrote:
> >
> > Our initial strategy to generate bundles for consumption by swupd
> > is to generate images which contain the base image (os-core) plus
> > the additional contents of the bundle, then prune out the core
> > contents. By generating images in this manner we hope to accomodate
> > packages which modify the rootfs outside of installing files, i.e.
> > with postinsts.
> >
> > To that end this class, to be used via BBCLASSEXTEND, will generate
> > virtual image recipes that add extra packages to the extended
> > image.
> Can this be combined with an image recipe which itself uses
> BBCLASSEXTEND to generate virtual image recipes, i.e. create a
> virtual
> recipes based on a virtual recipe?
Currently this doesn't work, but I've just filed a bug to handle this
scenario: https://bugzilla.yoctoproject.org/show_bug.cgi?id=9192
Regards,
Joshua
next prev parent reply other threads:[~2016-03-01 13:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 14:52 [PATCH 00/10] Integrate swupd software updater Joshua Lock
2016-02-24 14:52 ` [PATCH 01/10] rsync: add native variant Joshua Lock
2016-02-24 14:52 ` [PATCH 02/10] swupd-server: initial recipe 2.53 Joshua Lock
2016-02-25 8:11 ` Maciej Borzecki
2016-02-25 8:51 ` Joshua G Lock
2016-02-24 14:52 ` [PATCH 03/10] hardlink: add new recipe Joshua Lock
2016-02-24 21:00 ` Burton, Ross
2016-02-24 22:57 ` Andre McCurdy
2016-02-25 8:48 ` Joshua G Lock
2016-02-25 17:13 ` Mark Hatle
2016-02-25 21:40 ` Joshua G Lock
2016-02-25 21:57 ` Mark Hatle
2016-02-24 14:52 ` [PATCH 04/10] swupd-client: Add recipe Joshua Lock
2016-02-25 8:07 ` Maciej Borzecki
2016-02-25 8:50 ` Joshua G Lock
2016-02-24 14:52 ` [PATCH 05/10] swupdbundle: new class to generate virtual images for swupd-image Joshua Lock
2016-02-25 8:19 ` Maciej Borzecki
2016-02-25 8:47 ` Joshua G Lock
2016-02-25 17:06 ` Patrick Ohly
2016-03-01 13:45 ` Joshua G Lock [this message]
2016-02-24 14:52 ` [PATCH 06/10] swupd-image.bbclass: initial class to support swupd updater Joshua Lock
2016-02-24 14:52 ` [PATCH 07/10] oe-swupd-helpers: provide swupd-client required helper scripts and units Joshua Lock
2016-02-24 14:52 ` [PATCH 08/10] swupd-client: RDEPENDS on oe-swupd-helpers Joshua Lock
2016-02-24 14:52 ` [PATCH 09/10] swupd-client: enable native builds Joshua Lock
2016-02-24 14:52 ` [PATCH 10/10] os-release: sanitise VERSION_ID field Joshua Lock
2016-02-24 15:37 ` [PATCH 00/10] Integrate swupd software updater Patrick Ohly
2016-02-24 16:14 ` Joshua G Lock
[not found] ` <1456330147.5333.14.camel@intel.com>
2016-02-24 18:49 ` Patrick Ohly
2016-03-01 16:18 ` Joshua G Lock
2016-02-24 16:06 ` Trevor Woerner
2016-02-24 16:35 ` Philip Balister
2016-02-24 18:36 ` Maciej Borzecki
2016-02-24 19:51 ` Paul Eggleton
2016-02-24 20:40 ` Philip Balister
2016-02-25 21:42 ` Joshua G Lock
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=1456839944.3290.3.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox