From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [Build App RFC 2/5] image-vmdk: Add symbolic link
Date: Mon, 26 Mar 2012 11:23:53 -0700 [thread overview]
Message-ID: <4F70B439.3000400@linux.intel.com> (raw)
In-Reply-To: <321a1ce94fe3a79b6dfbd3c681c16b9452927167.1332744104.git.sgw@linux.intel.com>
The idea being what? To keep a short-name symlink to the longer named
actual image?
Please include a commit message.
On 03/25/2012 11:47 PM, Saul Wold wrote:
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/classes/image-vmdk.bbclass | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/meta/classes/image-vmdk.bbclass b/meta/classes/image-vmdk.bbclass
> index 3e63006..9d596cd 100644
> --- a/meta/classes/image-vmdk.bbclass
> +++ b/meta/classes/image-vmdk.bbclass
> @@ -10,6 +10,8 @@ inherit image-live
>
> create_vmdk_image () {
> qemu-img convert -O vmdk ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.hddimg ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.vmdk
> + ln -s ${IMAGE_NAME}.vmdk ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.vmdk
> +
> }
>
> python do_vmdkimg() {
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-03-26 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 6:47 [Build App RFC 0/5] Review Request for Build Appliance Saul Wold
2012-03-26 6:47 ` [Build App RFC 1/5] self-hosted-image: pre-populate the builder user with poky source Saul Wold
2012-03-26 6:47 ` [Build App RFC 2/5] image-vmdk: Add symbolic link Saul Wold
2012-03-26 18:23 ` Darren Hart [this message]
2012-03-26 6:47 ` [Build App RFC 3/5] boot-directdisk: Fix Block Calcuation Saul Wold
2012-03-26 18:26 ` Darren Hart
2012-03-26 6:47 ` [Build App RFC 4/5] vmdk: Update for direstdisk Saul Wold
2012-03-26 18:31 ` Darren Hart
2012-03-26 6:47 ` [Build App RFC 5/5] builder: Enable auto starting of Hob Saul Wold
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=4F70B439.3000400@linux.intel.com \
--to=dvhart@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