From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>,
Joao Henrique Ferreira de Freitas <joaohf@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boot-directdisk: fix the support of vmdk
Date: Fri, 20 Dec 2013 11:37:22 +0000 [thread overview]
Message-ID: <4597272.5pSZ6hOFRs@helios> (raw)
In-Reply-To: <20131220113238.GU3706@jama>
On Friday 20 December 2013 12:32:38 Martin Jansa wrote:
> On Fri, Dec 20, 2013 at 08:10:24AM -0200, Joao Henrique Ferreira de Freitas
> wrote:
> > Previous change (086ce22b88f5ef5f75a83119a32c8b3fdcfa296d) broke
> > the creating of vmdk images. This protects shell expansion variables
> > and let dd generate the image to be transformed to vmdk by
> > image-vmdk.class. ---
> >
> > meta/classes/boot-directdisk.bbclass | 16 ++++++----------
> > 1 file changed, 6 insertions(+), 10 deletions(-)
> >
> > diff --git a/meta/classes/boot-directdisk.bbclass
> > b/meta/classes/boot-directdisk.bbclass index 3277666..4f26f47 100644
> > --- a/meta/classes/boot-directdisk.bbclass
> > +++ b/meta/classes/boot-directdisk.bbclass
> > @@ -88,10 +88,10 @@ build_boot_dd() {
> >
> > grubefi_hddimg_populate $HDDDIR
> >
> > fi
> >
> > - if [ ${IMAGE_FSTYPE} = "vmdk" ]; then
> > - if [ x${AUTO_SYSLINUXMENU} = x1 ] ; then
> > + if [ "${IMAGE_FSTYPES}" = "vmdk" ]; then
> > + if [ "x${AUTO_SYSLINUXMENU}" = "x1" ] ; then
>
> IMAGE_FSTYPE looks really as typo, but what if there are multiple
> entries in IMAGE_FSTYPES?
>
> OE @ ~/openembedded-core $ git grep IMAGE_FSTYPE | grep -v IMAGE_FSTYPES
> meta/classes/boot-directdisk.bbclass: if [ ${IMAGE_FSTYPE} = "vmdk" ];
> then meta/classes/boot-directdisk.bbclass: if [ ${IMAGE_FSTYPE} != "vmdk"
> ]; then meta/classes/boot-directdisk.bbclass: if [ ${IMAGE_FSTYPE} !=
> "vmdk" ]; then
>
> Maybe you can use this variable instead:
> meta/classes/image.bbclass:IMAGE_TYPE_vmdk =
> '${@base_contains("IMAGE_FSTYPES", "vmdk", "image-vmdk", "", d)}'
I'd suggest not using that variable as it's an internal implementation detail
of image.bbclass - just use a similar base_contains() statement.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-12-20 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 10:10 [PATCH] boot-directdisk: fix the support of vmdk Joao Henrique Ferreira de Freitas
2013-12-20 11:32 ` Martin Jansa
2013-12-20 11:37 ` Paul Eggleton [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-23 6:50 Saul Wold
2014-01-23 7:04 ` Phil Blundell
2014-01-23 12:21 ` Richard Purdie
2014-01-23 12:36 ` Otavio Salvador
2014-01-23 11:21 ` Otavio Salvador
2014-06-05 5:11 ` yzhu1
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=4597272.5pSZ6hOFRs@helios \
--to=paul.eggleton@linux.intel.com \
--cc=joaohf@gmail.com \
--cc=martin.jansa@gmail.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