From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH 0/2] Consolidate multistrap configuration generation
Date: Wed, 14 Feb 2018 14:15:07 +0100 [thread overview]
Message-ID: <20180214131509.16361-1-claudius.heine.ext@siemens.com> (raw)
From: Claudius Heine <ch@denx.de>
Hi,
this patchset tries to consolidate the generation of the multistrap
configuration in the buildchroot and isar-image-base recipes to one.
This patchsetset also represents one part of the implementation of the
multi-repo support.
Cheers,
Claudius
Claudius Heine (2):
meta/classes/base: extend sys.path with lib directory
centralize multistrap configuration generation
.../recipes-core/images/files/multistrap.conf.in | 38 ----------
meta-isar/recipes-core/images/isar-image-base.bb | 33 ++++-----
meta/classes/base.bbclass | 24 +++++++
meta/lib/isar/__init__.py | 8 +++
meta/lib/isar/multistrap.py | 80 ++++++++++++++++++++++
meta/recipes-devtools/buildchroot/buildchroot.bb | 28 +++-----
.../buildchroot/files/multistrap.conf.in | 37 ----------
7 files changed, 134 insertions(+), 114 deletions(-)
delete mode 100644 meta-isar/recipes-core/images/files/multistrap.conf.in
create mode 100644 meta/lib/isar/__init__.py
create mode 100644 meta/lib/isar/multistrap.py
delete mode 100644 meta/recipes-devtools/buildchroot/files/multistrap.conf.in
--
2.15.1
next reply other threads:[~2018-02-14 13:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 13:15 claudius.heine.ext [this message]
2018-02-14 13:15 ` [PATCH 1/2] meta/classes/base: extend sys.path with lib directory claudius.heine.ext
2018-02-15 7:28 ` Jan Kiszka
2018-02-14 13:15 ` [PATCH 2/2] centralize multistrap configuration generation claudius.heine.ext
2018-02-15 7:28 ` Jan Kiszka
2018-02-15 8:16 ` Claudius Heine
2018-02-15 8:50 ` Jan Kiszka
2018-02-15 9:34 ` Alexander Smirnov
2018-02-15 10:05 ` Claudius Heine
2018-02-15 10:15 ` Jan Kiszka
2018-02-15 10:29 ` Alexander Smirnov
2018-02-15 11:27 ` Baurzhan Ismagulov
2018-02-15 13:17 ` Claudius Heine
2018-02-15 13:18 ` Jan Kiszka
2018-02-15 11:42 ` Baurzhan Ismagulov
2018-02-15 12:08 ` Claudius Heine
2018-02-15 12:37 ` Alexander Smirnov
2018-02-15 13:20 ` Claudius Heine
2018-02-15 13:39 ` Alexander Smirnov
2018-02-16 9:31 ` Claudius Heine
2018-02-16 10:35 ` Alexander Smirnov
2018-02-16 11:35 ` Jan Kiszka
2018-02-15 13:53 ` Jan Kiszka
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=20180214131509.16361-1-claudius.heine.ext@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@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