From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ian Reinhart Geiser <geiseri@geekcentral.pub>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Allow different filesystems to be used for VM images.
Date: Fri, 29 Apr 2016 09:19:00 +0100 [thread overview]
Message-ID: <1461917940.5465.74.camel@linuxfoundation.org> (raw)
In-Reply-To: <1461871306-2466-1-git-send-email-geiseri@geekcentral.pub>
On Thu, 2016-04-28 at 15:21 -0400, Ian Reinhart Geiser wrote:
> This allows for things like btrfs to be used vs just ext4.
> The default value of ext4 is kept so there is no functional
> change unless ROOTFS_TYPE is set in the inherting recipe.
>
> Signed-off-by: Ian Reinhart Geiser <geiseri@geekcentral.pub>
> ---
> meta/classes/image-vm.bbclass | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
This seems reasonable but could I ask you to use a variable name with
"VM" in the name please?
I appreciate some of the existing ones don't do this but moving forward
we need to try and better namespace some of these class specific
variables and this seems like a good place to start.
VM_ROOTFS_TYPE would be better for example (or VMIMG_ROOTFS_TYPE).
Cheers,
Richard
> diff --git a/meta/classes/image-vm.bbclass b/meta/classes/image
> -vm.bbclass
> index 47f7326..50d93d5 100644
> --- a/meta/classes/image-vm.bbclass
> +++ b/meta/classes/image-vm.bbclass
> @@ -23,16 +23,17 @@ do_bootdirectdisk[depends] += "dosfstools
> -native:do_populate_sysroot \
> syslinux-native:do_populate_sysroot \
> parted-native:do_populate_sysroot \
> mtools-native:do_populate_sysroot \
> - ${PN}:do_image_ext4 \
> + ${PN}:do_image_${ROOTFS_TYPE} \
> "
>
> -IMAGE_TYPEDEP_vmdk = "ext4"
> -IMAGE_TYPEDEP_vdi = "ext4"
> -IMAGE_TYPEDEP_qcow2 = "ext4"
> -IMAGE_TYPEDEP_hdddirect = "ext4"
> +IMAGE_TYPEDEP_vmdk = "${ROOTFS_TYPE}"
> +IMAGE_TYPEDEP_vdi = "${ROOTFS_TYPE}"
> +IMAGE_TYPEDEP_qcow2 = "${ROOTFS_TYPE}"
> +IMAGE_TYPEDEP_hdddirect = "${ROOTFS_TYPE}"
> IMAGE_TYPES_MASKED += "vmdk vdi qcow2 hdddirect"
>
> -ROOTFS ?= "${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.ext4"
> +ROOTFS_TYPE ?= "ext4"
> +ROOTFS ?= "${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.${ROOTFS_TYPE}"
>
> # Used by bootloader
> LABELS_VM ?= "boot"
> --
> 2.8.0.rc3
>
>
next prev parent reply other threads:[~2016-04-29 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 19:21 [PATCH] Allow different filesystems to be used for VM images Ian Reinhart Geiser
2016-04-29 8:19 ` Richard Purdie [this message]
2016-04-29 10:50 ` Ian Geiser
2016-04-29 11:10 ` Richard Purdie
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=1461917940.5465.74.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=geiseri@geekcentral.pub \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.