From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Baurzhan Ismagulov <ibr@radix50.net>,
chombourger@gmail.com,
Henning Schild <henning.schild@siemens.com>
Subject: [PATCHv3 0/9] a few cleanups a bug and a feature
Date: Thu, 7 Nov 2019 19:55:54 +0100 [thread overview]
Message-ID: <20191107185603.9077-1-henning.schild@siemens.com> (raw)
From: Henning Schild <henning.schild@siemens.com>
changes to v2:
* drop base-apt: use the "basename" command instead of pattern substitution
* stop the creation of the run.XX files for all recipes in p6 (v2 7)
The first 5 patches are pure cosmetic to clean up some things i stumbled
over when working on base-apt. I have a few more but they will come
later.
The series introduces the feature that Isar respects BB_NO_NETWORK,
p6+7.
p8 fixes a bug when using a not signed base-apt.
and the new p9 is also cosmetic
Henning Schild (9):
rootfs: fix incorrect feature name in comment
base_apt_helper: change variable names to increase readability
rootfs: rename ROOTFS_INSTALL_COMMAND lock to "isar-apt-lock"
dpkg-base: remove pointless ";" s at end of line
dpkg-base: fix indentation from tabs to spaces
base: implement BB_NO_NETWORK for apt-get
meta: do not equip rootfss with resolv.conf when BB_NO_NETWORK
bootstrap: fix debootstrap gpg issue when base-apt is not signed
meta: dpkg-gbp: remove unneeded proxy export
meta/classes/base-apt-helper.bbclass | 12 +++----
meta/classes/base.bbclass | 13 +++++++
meta/classes/buildchroot.bbclass | 10 ++++--
meta/classes/dpkg-base.bbclass | 34 +++++++++----------
meta/classes/dpkg-gbp.bbclass | 1 -
meta/classes/dpkg.bbclass | 4 +--
meta/classes/image-tools-extension.bbclass | 2 +-
meta/classes/rootfs.bbclass | 17 ++++++----
.../isar-bootstrap/isar-bootstrap.inc | 12 +++----
meta/recipes-kernel/linux/linux-custom.inc | 4 +--
10 files changed, 63 insertions(+), 46 deletions(-)
--
2.23.0
next reply other threads:[~2019-11-07 18:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 18:55 Henning Schild [this message]
2019-11-07 18:55 ` [PATCHv3 1/9] rootfs: fix incorrect feature name in comment Henning Schild
2019-11-07 18:55 ` [PATCHv3 2/9] base_apt_helper: change variable names to increase readability Henning Schild
2019-11-07 18:55 ` [PATCHv3 3/9] rootfs: rename ROOTFS_INSTALL_COMMAND lock to "isar-apt-lock" Henning Schild
2019-11-07 18:55 ` [PATCHv3 4/9] dpkg-base: remove pointless ";" s at end of line Henning Schild
2019-11-07 18:55 ` [PATCHv3 5/9] dpkg-base: fix indentation from tabs to spaces Henning Schild
2019-11-07 18:56 ` [PATCHv3 6/9] base: implement BB_NO_NETWORK for apt-get Henning Schild
2019-11-07 18:56 ` [PATCHv3 7/9] meta: do not equip rootfss with resolv.conf when BB_NO_NETWORK Henning Schild
2019-11-07 18:56 ` [PATCHv3 8/9] bootstrap: fix debootstrap gpg issue when base-apt is not signed Henning Schild
2019-11-14 20:11 ` Jan Kiszka
2019-11-14 21:45 ` Henning Schild
2019-11-15 6:07 ` Baurzhan Ismagulov
2019-11-07 18:56 ` [PATCHv3 9/9] meta: dpkg-gbp: remove unneeded proxy export Henning Schild
2019-11-12 16:39 ` [PATCHv3 0/9] a few cleanups a bug and a feature 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=20191107185603.9077-1-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--cc=chombourger@gmail.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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