public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "[ext] Q. Gylstorff" <Quirin.Gylstorff@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH] meta/classes: generate bill of material from image
Date: Tue, 6 Aug 2019 10:07:03 +0200	[thread overview]
Message-ID: <f4d9eed8-cb02-8958-b58f-d1975e9b98a3@siemens.com> (raw)
In-Reply-To: <20190805140742.11479-1-Quirin.Gylstorff@siemens.com>

Hi Quirin,

On 05/08/2019 16.07, [ext] 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:
> 
> source name| source version | binary package name | binary version
> 
> To use it add following line to the local.conf:
> ISAR_DO_PACKAGE_LIST ?= "1"

I would rather that the commit message would not suggest adding this to 
the local.conf and instead adding this to the image recipe variable 
scope, wherever that is a .bb, .bbclass, .bbappend or any .conf file.

> 
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> ---
>   meta-isar/conf/local.conf.sample                 |  4 ++++
>   .../classes/image-package-list-extension.bbclass | 16 ++++++++++++++++
>   meta/classes/image.bbclass                       |  1 +
>   3 files changed, 21 insertions(+)
>   create mode 100644 meta/classes/image-package-list-extension.bbclass
> 
> diff --git a/meta-isar/conf/local.conf.sample b/meta-isar/conf/local.conf.sample
> index 5b3a0a1..d188051 100644
> --- a/meta-isar/conf/local.conf.sample
> +++ b/meta-isar/conf/local.conf.sample
> @@ -170,6 +170,10 @@ IMAGE_INSTALL = "hello-isar example-raw example-module-${KERNEL_NAME} enable-fsc
>   # NOTE: this works on build host >= stretch for armhf, arm64 and amd64 targets for now.
>   ISAR_CROSS_COMPILE ?= "0"
>   
> +#
> +# Generate package list
> +ISAR_DO_PACKAGE_LIST ?= "1"
> +
>   #
>   # Uncomment this to enable use of cached base repository
>   #ISAR_USE_CACHED_BASE_REPO ?= "1"
> diff --git a/meta/classes/image-package-list-extension.bbclass b/meta/classes/image-package-list-extension.bbclass
> new file mode 100644
> index 0000000..558922e
> --- /dev/null
> +++ b/meta/classes/image-package-list-extension.bbclass
> @@ -0,0 +1,16 @@
> +# This software is a part of ISAR.
> +# Copyright (C) Siemens AG, 2019
> +#
> +# SPDX-License-Identifier: MIT
> +
> +ISAR_DO_PACKAGE_LIST ??= "0"
> +image_package_list[dirs] = "${DEPLOY_DIR_IMAGE}"
> +image_package_list() {

Its a postprocess function so call it 'image_postprocess_package_list' 
instead.

> +    if [ "${@repr(bb.utils.to_boolean(d.getVar('ISAR_DO_PACKAGE_LIST')))}" = 'True' ]; then

I don't like all those boolean values and tried to establish a better 
method using features. Take a look at the rootfs.bbclass, for example:

   ROOTFS_POSTPROCESS_COMMAND += 
"${@bb.utils.contains('ROOTFS_FEATURES', 'finalize-rootfs', 
'rootfs_postprocess_finalize', '', d)}"

You can adapt that. For instance like this:

   ROOTFS_POSTPROCESS_COMMAND += 
"${@bb.utils.contains('ROOTFS_FEATURES', 'generate-package-list', 
'image_postprocess_package_list', '', d)}"

Also it probably makes sense to have this as a default image feature. 
Otherwise people will not know about it and try to implement it themselves.

> +      dpkg-query --admindir=${IMAGE_ROOTFS}/var/lib/dpkg/ \
> +          -f '${source:Package}|${source:Version}|${binary:Package}|${Version}\n' -W > \
> +          ${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.packages.lst

As others have said, make it easily machine readable. JSON maybe?

Maybe something like:

   echo "[" > ${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.packages.lst
   dpkg-query ... -f '{"source_package": "${source:Package}", 
source_version": "${source:Version}", ...},\n' ... >> 
${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.packages.lst
   echo "]" >> ${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.packages.lst

Also maybe copy the licenses (/usr/share/doc/$package/copyright) 
somewhere? That might conflict with Hennings 'isar-exclude-docs' 
package, though... Maybe that can be changed to move them somewhere 
instead of removing them?

kind regards,
Claudius

> +    fi
> +}
> +ROOTFS_POSTPROCESS_COMMAND =+ "image_package_list"
> +
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index ec6bd39..85bab64 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -68,6 +68,7 @@ inherit image-tools-extension
>   inherit image-postproc-extension
>   inherit image-locales-extension
>   inherit image-account-extension
> +inherit image-package-list-extension
>   
>   # Extra space for rootfs in MB
>   ROOTFS_EXTRA ?= "64"
> 

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

  parent reply	other threads:[~2019-08-06  8:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 14:07 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 [this message]
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
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=f4d9eed8-cb02-8958-b58f-d1975e9b98a3@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=Quirin.Gylstorff@siemens.com \
    --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