Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: Gary Thomas <gary@mlbassoc.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: Create more than one image with WIC
Date: Tue, 14 Mar 2017 20:06:44 +0200	[thread overview]
Message-ID: <20170314180644.GA22000@linux.intel.com> (raw)
In-Reply-To: <1489513785.6396.83.camel@intel.com>

On Tue, Mar 14, 2017 at 06:49:45PM +0100, Patrick Ohly wrote:
> 
> > It's not a big deal to run wic sequentially to produce multiple images,
> > but it will create more problems than it solves I believe. It will be slower and
> > will make a mess in image naming in deploy directory.
> 
> I personally would prefer to support generating more than one wic image
> per image recipe. The different output files could be distinguished with
> an additional suffix (".efi.wic", ".live.wiC", etc.) where the suffix is
> either specified by the WKS file or the configuration where the WKS file
> is selected - the latter might be a bit more flexible.
>

From my point of view ths would be against the current design of oe
image building susbsystem. It would be also more complex and slower
unless we'll find a way to dynamically generate multiple image creation
tasks per one recipe and run them in parallel. In this case it will be
even more complex.

--
Regards,
Ed


  reply	other threads:[~2017-03-14 18:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  9:44 Create more than one image with WIC Daniel Schultz
2017-03-08 10:57 ` Ed Bartosh
2017-03-08 13:41   ` Gary Thomas
2017-03-08 13:43     ` Ed Bartosh
2017-03-13 16:16       ` Daniel Schultz
2017-03-14 17:11         ` Ed Bartosh
2017-03-14 17:49           ` Patrick Ohly
2017-03-14 18:06             ` Ed Bartosh [this message]
2017-03-15  7:24               ` Patrick Ohly
2017-03-15 12:58                 ` Ed Bartosh
2017-03-15 13:39                   ` Patrick Ohly
2017-03-15 13:41                     ` Patrick Ohly
2017-03-15 14:01                       ` Ed Bartosh
2017-03-15 14:47                         ` Ed Bartosh
2017-03-15 15:09                           ` Patrick Ohly
2017-03-15 15:04                         ` Patrick Ohly

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=20170314180644.GA22000@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=gary@mlbassoc.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