From: Heiko Thiery <heiko.thiery@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 00/12] pkg-stats json output improvements
Date: Mon, 2 Mar 2020 15:50:02 +0100 [thread overview]
Message-ID: <20200302145013.9574-1-heiko.thiery@gmail.com> (raw)
- add developers information to the packages
- add supported defconfigs to json
- add license information to json
- add license file information to json
- add patch files to json
- add a more generic check status field to the packages for easier post
processing. The following check status are availble: checks: cve, license,
license-files, hash, hash-license,patches, version, url, developers,
pkg-check
---
v3 -> v4:
Included the review comments from Titouan
- use only one signed-off mail address
- do some things in a more pythonic way
- remove the patch_count attribute and use a class property instead
(Note that the patch_count value will not go into the json output
anymore,but then coutn can be computed by "len(patch_files)".)
- remove the status initializer in the package class that was introduced
in v3
- update the cve status at the end of the cve check loop
- change the is_valid_infra -> has_valid_infra and use it as property
v2 -> v3:
- keep variable latest_release but change format
- add check for license file hashes
- introduce a na status for the checks
- add a list of all possible checks to the json output
- add the cve check status
v1 -> v2:
- cleanup and recreation of patches
- remove pkg name from dumping to json
- use patch_files instead of combine count and files in dict
- include getdevelopers.py to reuse Developers class
---
Heiko Thiery (12):
support/scripts/pkg-stats: store latest version in a dict
support/scripts/pkg-stats: store patch files for the package
support/scripts/pkg-stats: set developers info
support/scripts/pkg-stats: store licences of package
support/scripts/pkg-stats: add package status
support/scripts/pkg-stats: add package count to stats
support/scripts/pkg-stats: store pkg dir path
support/scripts/pkg-stats: add defconfig support
support/scripts/pkg-stats: add support for license hash check
support/scripts/pkg-stats: set status to 'na' for virtual packages
support/scripts/pkg-stats: initialize all package status checks
support/scripts/pkg-stats: add status for cve check
support/scripts/pkg-stats | 271 +++++++++++++++++++++++++++++---------
1 file changed, 211 insertions(+), 60 deletions(-)
--
2.20.1
next reply other threads:[~2020-03-02 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 14:50 Heiko Thiery [this message]
2020-03-02 14:50 ` [Buildroot] [PATCH v4 01/12] support/scripts/pkg-stats: store latest version in a dict Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 02/12] support/scripts/pkg-stats: store patch files for the package Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 03/12] support/scripts/pkg-stats: set developers info Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 04/12] support/scripts/pkg-stats: store licences of package Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 05/12] support/scripts/pkg-stats: add package status Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 06/12] support/scripts/pkg-stats: add package count to stats Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 07/12] support/scripts/pkg-stats: store pkg dir path Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 08/12] support/scripts/pkg-stats: add defconfig support Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 09/12] support/scripts/pkg-stats: add support for license hash check Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 10/12] support/scripts/pkg-stats: set status to 'na' for virtual packages Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 11/12] support/scripts/pkg-stats: add list of status checks to the json output Heiko Thiery
2020-03-02 14:50 ` [Buildroot] [PATCH v4 12/12] support/scripts/pkg-stats: add status for cve check Heiko Thiery
2020-03-06 16:46 ` [Buildroot] [PATCH v4 00/12] pkg-stats json output improvements Titouan Christophe
2020-03-06 18:32 ` Heiko Thiery
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=20200302145013.9574-1-heiko.thiery@gmail.com \
--to=heiko.thiery@gmail.com \
--cc=buildroot@busybox.net \
/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