Re: [PATCH v2] meta/classes: generate bill of material from image

[Claudius Heine <claudius.heine.ext@siemens.com>]

Hi Gernot,

On 07/08/2019 12.00, 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.

Ok, those are points I haven't considered. That would point to a more 
common CSV format with '[,;\t ]' separators. This can easily imported in 
MS Office 180.

This script currently uses the dpkg-query of the build system, not the 
one from the buildchroot or image root fs, so the file cannot be created 
easily on other non-debian systems. @Quirin: Have you tried using the 
dpkg-query of the buildchroot?

regards,
Claudius

-- 
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