From: Jan Kiszka <jan.kiszka@siemens.com>
To: Harald Seiler <hws@denx.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] meta: Add targz image class
Date: Tue, 20 Nov 2018 12:54:04 +0100 [thread overview]
Message-ID: <2e5f28bd-30d4-56ce-3605-42981e2348ec@siemens.com> (raw)
In-Reply-To: <525a1c5b7730f98e1236e1596cf31dc3e23e1b5e.camel@denx.de>
On 20.11.18 12:50, Harald Seiler wrote:
> Signed-off-by: Harald Seiler <hws@denx.de>
> ---
> meta/classes/targz-img.bbclass | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
> create mode 100644 meta/classes/targz-img.bbclass
>
> diff --git a/meta/classes/targz-img.bbclass b/meta/classes/targz-img.bbclass
> new file mode 100644
> index 0000000..898c2a8
> --- /dev/null
> +++ b/meta/classes/targz-img.bbclass
> @@ -0,0 +1,12 @@
> +# This software is a part of ISAR.
Missing copyright and license statement. That should be something like
# This software is a part of ISAR.
# Copyright (c) Siemens AG, 2018
#
# SPDX-License-Identifier: MIT
("Siemens" if this was part of our contract work)
> +
> +TARGZ_IMAGE_FILE = "${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.tar.gz"
> +
> +do_targz_image[stamp-extra-info] = "${DISTRO}-${MACHINE}"
> +
> +do_targz_image() {
> + rm -f ${TARGZ_IMAGE_FILE}
> + sudo tar -cvzf ${TARGZ_IMAGE_FILE} -C ${IMAGE_ROOTFS} .
We need sudo in order to see files that are root-visible only, right?
> +}
> +
> +addtask targz_image before do_build after do_copy_boot_files
>
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-11-20 11:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 11:50 Harald Seiler
2018-11-20 11:54 ` Jan Kiszka [this message]
2018-11-20 12:51 ` Henning Schild
2018-11-20 13:07 ` Harald Seiler
2018-11-20 13:14 ` chombourger
2018-11-20 13:19 ` [PATCH v2] " Harald Seiler
2018-11-23 7:32 ` Maxim Yu. Osipov
2018-11-23 11:38 ` Harald Seiler
2018-11-24 14:01 ` Cedric Hombourger
2018-11-27 9:13 ` [PATCH v3] " Harald Seiler
2018-12-10 12:04 ` Maxim Yu. Osipov
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=2e5f28bd-30d4-56ce-3605-42981e2348ec@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=hws@denx.de \
--cc=isar-users@googlegroups.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