From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH 0/5] Rework isar-apt v2
Date: Mon, 5 Feb 2018 12:59:26 +0300 [thread overview]
Message-ID: <20180205095931.23903-1-asmirnov@ilbers.de> (raw)
Hi all,
this series intended to make buildchroot able to work with isar-apt.
I've tried to add extended comments to each patch.
Impact: with this series I'm able to build 'example-hello' <-> 'libhello'
without any hacks. So the deps are installed automatically.
Changes since v1:
- The bitbake was updated to the latest upstream version
- In build.sh the only isar-apt is updated
Alexander Smirnov (5):
Update isar-bitbake.conf according to the changes in bitbake related
to multiconfig support.
isar-apt: Introduce separate recipe
buildchroot: Enable isar-apt
build.sh: Update apt sources
build.sh: Force 'yes' for apt
meta-isar/conf/local.conf.sample | 5 +-
.../recipes-core/images/files/distributions.in | 3 -
meta/classes/dpkg-base.bbclass | 12 +++-
meta/classes/image.bbclass | 67 +---------------------
meta/classes/isar-events.bbclass | 20 +++++++
meta/conf/isar-bitbake.conf | 1 +
meta/recipes-devtools/buildchroot/buildchroot.bb | 7 +++
meta/recipes-devtools/buildchroot/files/build.sh | 13 ++++-
.../buildchroot/files/multistrap.conf.in | 8 ++-
.../isar-apt/files/distributions.in | 3 +
meta/recipes-devtools/isar-apt/isar-apt.bb | 29 ++++++++++
11 files changed, 92 insertions(+), 76 deletions(-)
delete mode 100644 meta-isar/recipes-core/images/files/distributions.in
create mode 100644 meta/classes/isar-events.bbclass
create mode 100644 meta/recipes-devtools/isar-apt/files/distributions.in
create mode 100644 meta/recipes-devtools/isar-apt/isar-apt.bb
--
2.1.4
next reply other threads:[~2018-02-05 9:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 9:59 Alexander Smirnov [this message]
2018-02-05 9:59 ` [PATCH 1/5] Update isar-bitbake.conf according to the changes in bitbake related to multiconfig support Alexander Smirnov
2018-02-05 10:15 ` Jan Kiszka
2018-02-05 10:26 ` Alexander Smirnov
2018-02-05 10:27 ` Jan Kiszka
2018-02-05 9:59 ` [PATCH 2/5] isar-apt: Introduce separate recipe Alexander Smirnov
2018-02-05 9:59 ` [PATCH 3/5] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-05 10:18 ` Jan Kiszka
2018-02-05 10:33 ` Alexander Smirnov
2018-02-05 9:59 ` [PATCH 4/5] build.sh: Update apt sources Alexander Smirnov
2018-02-05 9:59 ` [PATCH 5/5] build.sh: Force 'yes' for apt Alexander Smirnov
2018-02-05 11:52 ` Jan Kiszka
2018-02-05 13:56 ` Alexander Smirnov
2018-02-05 13:48 ` [PATCH 3/5 v2] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-06 11:01 ` [PATCH 3/5 v3] " Alexander Smirnov
2018-02-06 12:10 ` Jan Kiszka
2018-02-06 13:28 ` Alexander Smirnov
2018-02-05 14:41 ` [PATCH 0/5] Rework isar-apt v2 Alexander Smirnov
2018-02-05 16:47 ` Jan Kiszka
2018-02-05 16:56 ` Alexander Smirnov
2018-02-06 13:57 ` [PATCH 3/5 v4] buildchroot: Enable isar-apt Alexander Smirnov
2018-02-06 17:31 ` Jan Kiszka
2018-02-06 18:29 ` Alexander Smirnov
2018-02-06 18:31 ` Jan Kiszka
2018-02-08 14:37 ` Henning Schild
2018-02-08 14:57 ` Alexander Smirnov
2018-02-06 20:24 ` [PATCH 0/5] Rework isar-apt v2 Alexander Smirnov
2018-02-08 14:59 ` Henning Schild
2018-02-08 15:09 ` Jan Kiszka
2018-02-09 10:30 ` Henning Schild
2018-02-08 17:03 ` Benedikt Niedermayr
2018-02-08 18:27 ` Benedikt Niedermayr
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=20180205095931.23903-1-asmirnov@ilbers.de \
--to=asmirnov@ilbers.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