From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2] meta/classes: generate bill of material from image
Date: Wed, 7 Aug 2019 12:59:33 +0200 [thread overview]
Message-ID: <20190807105933.GL32438@yssyq.m.ilbers.de> (raw)
In-Reply-To: <c3287e52-704a-77a4-f7c8-b5f45b34abf8@siemens.com>
On Wed, Aug 07, 2019 at 12:00:22PM +0200, Gernot Hillier wrote:
> Am 07.08.19 um 10:29 schrieb Gernot Hillier:
> > > We don't need an additional dependency in isar. But if you like to
> > > use json in a shell script, jq might be the way to go.
> >
> > The main use case for such manifests is decoupled from the build
> > process, i.e. far away from Isar and probably even using such strange
> > platforms like Windows. Think about clearing personnel who wants to
> > postprocess such lists in their MS Office world
>
> And another important point I forgot: those manifests should be easy to
> create on targets/VMs without Isar or any other additional tool.
>
> We will continue to have Debian images which were not created with Isar and
> we can also safely assume that some development teams will manually modify
> Isar images later on.
>
> So we need some format which can be easily created using a simple shell
> command which works on virtually any Debian image.
I second Gernot's both points. If Isar already implements it differently, I
wouldn't necessarily block the patch since it adds value today, but I think
simple Yocto-like format and standalone generation is the right direction to
go. Other formats could be e.g. optional or additional.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-08-07 10:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:07 [PATCH] " Q. Gylstorff
2019-08-05 14:37 ` vijai kumar
2019-08-05 14:43 ` Henning Schild
2019-08-05 14:48 ` Jan Kiszka
2019-08-05 15:08 ` Henning Schild
2019-08-05 15:10 ` Jan Kiszka
2019-08-05 15:00 ` Baurzhan Ismagulov
2019-08-06 8:07 ` Claudius Heine
2019-08-06 8:36 ` Baurzhan Ismagulov
2019-08-06 8:47 ` Claudius Heine
2019-08-06 9:03 ` Baurzhan Ismagulov
2019-08-06 10:38 ` Claudius Heine
2019-08-06 8:38 ` Jan Kiszka
2019-08-06 8:48 ` Claudius Heine
2019-08-06 10:51 ` Quirin Gylstorff
2019-08-06 13:55 ` [PATCH v2] " Q. Gylstorff
2019-08-07 7:52 ` Quirin Gylstorff
2019-08-07 7:56 ` Gernot Hillier
2019-08-07 8:01 ` Claudius Heine
2019-08-07 8:08 ` Gernot Hillier
2019-08-07 8:21 ` Claudius Heine
2019-08-07 8:29 ` Gernot Hillier
2019-08-07 10:00 ` Gernot Hillier
2019-08-07 10:59 ` Baurzhan Ismagulov [this message]
2019-08-07 11:27 ` Claudius Heine
2019-08-07 12:27 ` Quirin Gylstorff
2019-08-09 10:30 ` [PATCH v3] " Q. Gylstorff
2019-08-12 8:04 ` Claudius Heine
2019-08-12 9:09 ` Quirin Gylstorff
2019-08-12 9:57 ` Claudius Heine
2019-08-13 8:18 ` [PATCH v4] " Q. Gylstorff
2019-08-13 8:53 ` Claudius Heine
2019-08-13 13:40 ` [PATCH v5] " Q. Gylstorff
2019-09-21 13:02 ` Jan Kiszka
2019-09-23 12:25 ` [PATCH v6] " Q. Gylstorff
2019-09-23 13:51 ` [PATCH v7] " Q. Gylstorff
2019-10-16 12:26 ` 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=20190807105933.GL32438@yssyq.m.ilbers.de \
--to=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