From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Gernot Hillier <gernot.hillier@siemens.com>,
Quirin Gylstorff <quirin.gylstorff@siemens.com>,
isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH v2] meta/classes: generate bill of material from image
Date: Wed, 7 Aug 2019 10:21:57 +0200 [thread overview]
Message-ID: <2d098930-f919-47fb-44e3-3429f9be04ca@siemens.com> (raw)
In-Reply-To: <a88c1291-a820-7e00-5947-8cace59b5822@siemens.com>
On 07/08/2019 10.08, Gernot Hillier wrote:
>
>
> Am 07.08.19 um 10:01 schrieb Claudius Heine:
>> Hi Gernot,
>>
>> On 07/08/2019 09.56, [ext] Gernot Hillier wrote:
>>> Hi!
>>>
>>> Am 07.08.19 um 09:52 schrieb Quirin Gylstorff:
>>>>
>>>>
>>>> On 8/6/19 3:55 PM, Q. Gylstorff wrote:
>>>>> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>>>>
>>>>> To create products it is necessary to have a list
>>>>> of used packages for clearance and to security monitoring.
>>>>> To get a simple list of packages use dpkg-query and generate
>>>>> a list with the following pattern:
>>>>>
>>> [...]
>>>> I am thinking about adding json as alternative output format. The yocto
>>>
>>> Why? Is this some established standard somewhere else?
>>
>> I don't know any standard format for manifest files? Do you? I
>> suggested JSON because its very easy machine readable and expandable
>> without breaking other tools.
>
> Well, if there's no established standard, I'd prefer to go with
> something which is easy to consume in shell scripts.
>
> If we don't have clear advantages for JSON, I prefer
Well IMO, we do have a clear advantage being JSON is sort of a standard
format and this is not. But we could go with CSV perhaps?
>
> cut -d "|" -f 1
>
> over
>
> python3 -c "import sys, json; print(json.load(sys.stdin)['name'])"
>
> - or adding another dependency to "jq".
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.
Otherwise we could also use the debian format and print out the
installed packages in deb822 [1] format.
regards,
Claudius
[1] http://man7.org/linux/man-pages/man5/deb822.5.html
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2019-08-07 8:21 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 [this message]
2019-08-07 8:29 ` Gernot Hillier
2019-08-07 10:00 ` Gernot Hillier
2019-08-07 10:59 ` Baurzhan Ismagulov
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=2d098930-f919-47fb-44e3-3429f9be04ca@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@denx.de \
--cc=gernot.hillier@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=quirin.gylstorff@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