From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bootimg-efi.py: Use IMGDEPLOYDIR instead of DEPLOY_DIR_IMAGE for initrd
Date: Mon, 3 Jul 2017 12:06:06 +0300 [thread overview]
Message-ID: <20170703090606.GB5571@linux.intel.com> (raw)
In-Reply-To: <6aef97ed-8284-039a-c780-c5b01ee8fe1a@linux.intel.com>
On Sat, Jul 01, 2017 at 04:48:41PM -0500, Alejandro Hernandez wrote:
>
>
> > From the DESCRIPTION:
> >
> > core-image-tiny-initramfs doesn't actually generate an image but
> > rather generates boot and rootfs artifacts into a common
> > location that can subsequently be picked up by external image
> > generation tools such as wic.
> This is the old description, when it was though that we would have a common
> artifacts directory, which never happened due to some changes in wic
> last year
Can you elaborate on this please?
I'm still thinking that having a common artifacts directory is what we
should aim for. And DEPLOY_DIR_IMAGE is a good candidate for it as most
of artifacts are already there.
--
Regards,
Ed
next prev parent reply other threads:[~2017-07-03 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 17:53 [PATCH] bootimg-efi.py: Use IMGDEPLOYDIR instead of DEPLOY_DIR_IMAGE for initrd Alejandro Hernandez
2017-06-30 18:43 ` Patrick Ohly
2017-06-30 20:38 ` Alejandro Hernandez
2017-07-01 15:09 ` Patrick Ohly
2017-07-01 21:48 ` Alejandro Hernandez
2017-07-03 6:45 ` Patrick Ohly
2017-07-03 9:06 ` Ed Bartosh [this message]
2017-07-03 8:36 ` Ed Bartosh
2017-07-03 9:27 ` Patrick Ohly
2017-07-03 12:44 ` Ed Bartosh
2017-07-03 14:10 ` 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=20170703090606.GB5571@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=alejandro.hernandez@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox