From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
Alexander Smirnov <asmirnov@ilbers.de>,
isar-users@googlegroups.com, Baurzhan Ismagulov <ibr@radix50.net>
Subject: Re: [PATCH 2/2] centralize multistrap configuration generation
Date: Thu, 15 Feb 2018 14:53:09 +0100 [thread overview]
Message-ID: <7f11423f-80b3-8aea-5587-d0be632aea9d@siemens.com> (raw)
In-Reply-To: <b8836d58-c295-a218-9be2-64bdca5b24da@siemens.com>
On 2018-02-15 14:20, [ext] Claudius Heine wrote:
>> It might be possible to extent the multiconfig with
>>> shell scripting, but I prefer using python for such advanced logic.
>>
>> I don't care about python or bash
>
> At least Baurzhan seems to care, because he doesn't like debootstrap
> because of it being in shell.
>
That's not a major argument. For us, debootstrap a tool with an API. If
we can use that API without bending it, it's fine. If we can improve our
use case by enhancing it upstream later on, it's perfect. Otherwise, we
need to model Debian bootstrap after the community pattern with our own
languages (shell and python).
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-02-15 13:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 13:15 [PATCH 0/2] Consolidate " claudius.heine.ext
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 [this message]
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=7f11423f-80b3-8aea-5587-d0be632aea9d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=claudius.heine.ext@siemens.com \
--cc=ibr@radix50.net \
--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