From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] pkg-stats support for external tree?
Date: Thu, 15 Oct 2020 08:57:53 +0200 [thread overview]
Message-ID: <20201015085753.33f3b15e@windsurf> (raw)
In-Reply-To: <HE1PR03MB298830C6E778223631A2A08AF0020@HE1PR03MB2988.eurprd03.prod.outlook.com>
Hello Magnus,
On Thu, 15 Oct 2020 04:31:11 +0000
Magnus Armholt <magnus.armholt@wapice.com> wrote:
> We are using a setup with an external tree holding our specific packages (br2_external).
> The renewed pkg-stats is a nice tool and we would like to cover also our specific packages in br2_external.
> Is this possible?
>
> I tried running the pkg-stats from our base directory (parent of
> buildroot) but this fails due to how the utils/getdeveloperlib is
> included.
Indeed, there is no support for BR2_EXTERNAL in pkg-stats. In fact,
pkg-stats is more a tool for the Buildroot community to keep an eye on
all packages that are in the official Buildroot.
A Buildroot user (or a company using Buildroot) would I guess be more
interested in pkg-stats-like results, but limited to their package
selection.
Recently, we've added support/scripts/cve-checker which output a HTML
page looking like the pkg-stats output, but with just your package +
the CVEs that affect them (if any). However, it does not output all the
same information as pkg-stats.
Which specific information of pkg-stats do you find useful ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-10-15 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 4:31 [Buildroot] pkg-stats support for external tree? Magnus Armholt
2020-10-15 6:57 ` Thomas Petazzoni [this message]
2020-10-15 7:49 ` Magnus Armholt
2020-10-15 8:17 ` Thomas Petazzoni
2020-10-15 8:56 ` Magnus Armholt
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=20201015085753.33f3b15e@windsurf \
--to=thomas.petazzoni@bootlin.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