From: Zhihang Wei <wzh@ilbers.de>
To: vidyasagar.gc@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH] imagetypes_vm: clean up intermediate ova artifacts
Date: Mon, 24 Aug 2026 11:41:07 +0200 [thread overview]
Message-ID: <1cd988fb-e850-4a8c-803e-f204bd2507da@ilbers.de> (raw)
In-Reply-To: <20260813034129.2393-1-vidyasagar.gc@siemens.com>
Applied to next, thanks.
Zhihang
On 8/13/26 05:41, vidyasagar.gc via isar-users wrote:
> From: Vidyasagar G C <vidyasagar.gc@siemens.com>
>
> The ovf descriptor, manifest, and vmdk image are only required
> while assembling the ova image. Remove these intermediate artifacts
> after the ova has been successfully created, leaving only the
> final ova image in the deployment directory.
>
> Signed-off-by: Vidyasagar G C <vidyasagar.gc@siemens.com>
> ---
> meta/classes-recipe/imagetypes_vm.bbclass | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes-recipe/imagetypes_vm.bbclass b/meta/classes-recipe/imagetypes_vm.bbclass
> index 62eb9600..9f1f4c48 100644
> --- a/meta/classes-recipe/imagetypes_vm.bbclass
> +++ b/meta/classes-recipe/imagetypes_vm.bbclass
> @@ -71,8 +71,6 @@ IMAGE_CMD:ova() {
> exit 0
> fi
> rm -f '${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.ova'
> - rm -f '${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.ovf'
> - rm -f '${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.mf'
>
> export PRIMARY_MAC=$(macgen)
> export LAST_CHANGE=$(date -u "+%Y-%m-%dT%H:%M:%SZ")
> @@ -95,6 +93,9 @@ IMAGE_CMD:ova() {
> tar -uvf ${PP_DEPLOY}/${IMAGE_FULLNAME}.ova -C ${PP_DEPLOY} ${IMAGE_FULLNAME}.mf
> fi
> tar -uvf ${PP_DEPLOY}/${IMAGE_FULLNAME}.ova -C ${PP_DEPLOY} ${VIRTUAL_MACHINE_IMAGE_FILE}
> + rm -f '${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.mf'
> + rm -f '${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.ovf'
> + rm -f '${DEPLOY_DIR_IMAGE}/${VIRTUAL_MACHINE_IMAGE_FILE}'
> EOIMAGER
> }
> IMAGE_CMD:ova[depends] = "${PN}:do_transform_template"
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/1cd988fb-e850-4a8c-803e-f204bd2507da%40ilbers.de.
prev parent reply other threads:[~2026-08-24 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 3:41 vidyasagar.gc via isar-users
2026-08-24 9:41 ` Zhihang Wei [this message]
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=1cd988fb-e850-4a8c-803e-f204bd2507da@ilbers.de \
--to=wzh@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=vidyasagar.gc@siemens.com \
/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