From: Jan Kiszka <jan.kiszka@siemens.com>
To: vijaikumar.kanagarajan@gmail.com, isar-users@googlegroups.com,
henning.schild@siemens.com, claudius.heine.ext@siemens.com
Cc: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
Subject: Re: [PATCH] Remove unwanted inherits of base-apt-helper
Date: Mon, 19 Aug 2019 13:25:53 +0200 [thread overview]
Message-ID: <b36a7e87-b4de-c46b-df75-daa51bca585a@siemens.com> (raw)
In-Reply-To: <20190819105447.5852-1-Vijaikumar_Kangarajan@mentor.com>
On 19.08.19 12:54, vijaikumar.kanagarajan@gmail.com wrote:
> From: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
>
> After bff4e89a changes, we do not require to inherit the base-apt-helper
> class in isar-bootstrap.inc and base-apt.bb files. Remove them.
>
> Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
> ---
> meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 2 --
> meta/recipes-devtools/base-apt/base-apt.bb | 2 --
> 2 files changed, 4 deletions(-)
>
> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> index ff8ab01..3410b64 100644
> --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> @@ -32,8 +32,6 @@ HOST_DISTRO_APT_SOURCES += "conf/distro/${HOST_DISTRO}.list"
>
> DISTRO_APT_PREMIRRORS ?= "${@ "http://ftp\.(\S+\.)?debian.org/\S* file:///${REPO_BASE_DIR}/${BASE_DISTRO} \n" if bb.utils.to_boolean(d.getVar('ISAR_USE_CACHED_BASE_REPO')) else "" }"
>
> -inherit base-apt-helper
> -
> python () {
> distro_bootstrap_keys = (d.getVar("DISTRO_BOOTSTRAP_KEYS", False) or "").split()
>
> diff --git a/meta/recipes-devtools/base-apt/base-apt.bb b/meta/recipes-devtools/base-apt/base-apt.bb
> index 1c0b4c6..9f55ad5 100644
> --- a/meta/recipes-devtools/base-apt/base-apt.bb
> +++ b/meta/recipes-devtools/base-apt/base-apt.bb
> @@ -3,8 +3,6 @@
>
> SRC_URI = "file://distributions.in"
>
> -inherit base-apt-helper
> -
> BASE_REPO_KEY ?= ""
>
> CACHE_CONF_DIR = "${REPO_BASE_DIR}/${BASE_DISTRO}/conf"
>
Good cleanup, thanks.
Reviewed-by: Jan Kiszka <jan.kiszka@siemens.com>
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-08-19 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 10:54 vijaikumar.kanagarajan
2019-08-19 11:25 ` Jan Kiszka [this message]
2019-09-04 12:28 ` Baurzhan Ismagulov
2019-09-04 17:51 ` Vijai Kumar K
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=b36a7e87-b4de-c46b-df75-daa51bca585a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=vijaikumar.kanagarajan@gmail.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