From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Quirin Gylstorff" <quirin.gylstorff@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta/classes:Add wic tooling for related images
Date: Tue, 23 Jul 2019 16:18:50 +0200 [thread overview]
Message-ID: <20190723161850.0bdb81eb@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190723134947.20714-1-quirin.gylstorff@siemens.com>
I do not remember why it is done like that. The original code most
likely came from me. But probably at a time where IMAGER_INSTALL did
not yet exist. So it effectively messed with IMAGE_PREINSTALL.
Would have to go back in history and read changes. If my assumption
(legacy left overs from before IMAGER_INSTALL) is correct this patch is
probably correct. But maybe there is another reason.
Did you go back a few "git blame"s and read the commit messages and
comments around the python function?
Henning
Am Tue, 23 Jul 2019 15:49:47 +0200
schrieb "[ext] Quirin Gylstorff" <quirin.gylstorff@siemens.com>:
> The dependencies for wic are only added if IMAGE_TYPE
> is equal to "wic-img". If a image type depends on the
> wic-image class it is no longer possible to build a
> wic image.
>
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> ---
> meta/classes/image-tools-extension.bbclass | 6 ------
> meta/classes/wic-img.bbclass | 4 ++++
> 2 files changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/meta/classes/image-tools-extension.bbclass
> b/meta/classes/image-tools-extension.bbclass index b8672d5..ca94d49
> 100644 --- a/meta/classes/image-tools-extension.bbclass
> +++ b/meta/classes/image-tools-extension.bbclass
> @@ -14,12 +14,6 @@ IMAGER_INSTALL ??= ""
> IMAGER_BUILD_DEPS ??= ""
> DEPENDS += "${IMAGER_BUILD_DEPS}"
>
> -python () {
> - if d.getVar('IMAGE_TYPE', True) == 'wic-img':
> - d.appendVar('IMAGER_INSTALL',
> - ' ' + d.getVar('WIC_IMAGER_INSTALL', True))
> -}
> -
> do_install_imager_deps[depends] = "buildchroot-target:do_build"
> do_install_imager_deps[deptask] = "do_deploy_deb"
> do_install_imager_deps[lockfiles] += "${REPO_ISAR_DIR}/isar.lock"
> diff --git a/meta/classes/wic-img.bbclass
> b/meta/classes/wic-img.bbclass index 94f0b02..eee27b3 100644
> --- a/meta/classes/wic-img.bbclass
> +++ b/meta/classes/wic-img.bbclass
> @@ -11,6 +11,10 @@ do_copy_wks_template () {
> cp -f '${WKS_TEMPLATE_PATH}' '${WORKDIR}/${WKS_TEMPLATE_FILE}'
> }
>
> +
> +IMAGER_INSTALL = ${WIC_IMAGER_INSTALL}
> +
> +
> python () {
> import itertools
> import re
next prev parent reply other threads:[~2019-07-23 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 13:49 Quirin Gylstorff
2019-07-23 14:18 ` Henning Schild [this message]
2019-07-23 14:42 ` Quirin Gylstorff
2019-07-23 14:56 ` Claudius Heine
2019-07-23 15:15 ` Henning Schild
2019-07-23 15:24 ` Jan Kiszka
2019-07-23 15:04 ` [PATCH v2] " Quirin Gylstorff
2019-07-23 15:08 ` Claudius Heine
2019-07-25 10:20 ` [PATCH v3] " Quirin Gylstorff
2019-08-01 4:26 ` Baurzhan Ismagulov
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=20190723161850.0bdb81eb@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=quirin.gylstorff@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