From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] image.py: write bitbake variables to .env file
Date: Mon, 31 Aug 2015 14:14:53 +0300 [thread overview]
Message-ID: <20150831111453.GA28923@linux.intel.com> (raw)
In-Reply-To: <CABcZANkADU6Ttr+6ZWGcH51Ue_Au++5ULxfN1__p4z+zcJYi6g@mail.gmail.com>
On Sun, Aug 30, 2015 at 09:22:50PM -0700, Christopher Larson wrote:
> On Sun, Aug 30, 2015 at 2:14 PM, Ed Bartosh <ed.bartosh@linux.intel.com>
> wrote:
>
> > Write set of bitbake variables used by wic into
> > build/tmp/sysroots/<machine>/imagedata/<image>.env
> >
> > List of variables is defined in WICVARS variable in
> > meta/classes/image_types.bbclass.
> >
> > This is needed for wic to be able to get bitbake variables without
> > running 'bitbake -e'.
> >
> > Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> >
>
> The function name (_write_env) sounds generic, as does the commit message,
> and the filename, yet it relies on a variable which is WIC-specific. This
> seems rather inconsistent to me, either this thing is for wic alone, or it
> isn't, and the function name, file name, and variable name should reflect
> that.
Thanks for pointing this out. I'll rename _write_env to _write_wic_env it in the next patchset.
--
Regards,
Ed
next prev parent reply other threads:[~2015-08-31 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 21:14 [PATCH 0/5] V4: Build wic images with bitbake Ed Bartosh
2015-08-30 21:14 ` [PATCH 1/5] image.py: write bitbake variables to .env file Ed Bartosh
2015-08-31 4:22 ` Christopher Larson
2015-08-31 11:14 ` Ed Bartosh [this message]
2015-08-30 21:14 ` [PATCH 2/5] oe-selftest: test generation of <image>.env Ed Bartosh
2015-08-30 21:14 ` [PATCH 3/5] wic-image-minimal: add wic image recipe and .wks Ed Bartosh
2015-08-30 21:14 ` [PATCH 4/5] oe-selftest: test building wic image by bitbake Ed Bartosh
2015-08-30 21:14 ` [PATCH 5/5] wic: use bitbake variable ROOTFS_SIZE Ed Bartosh
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=20150831111453.GA28923@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=clarson@kergoth.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