From: Matthew Weber <matthew.weber@collins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: indicate proper CPE prefix
Date: Thu, 7 Jan 2021 15:26:43 -0600 [thread overview]
Message-ID: <CANQCQpZ6Z_YGkCUWLT+gHz9=LRFKD8L+cvJcWQMp53v1KA3smg@mail.gmail.com> (raw)
In-Reply-To: <20210107211336.3030397-1-thomas.petazzoni@bootlin.com>
Thomas,
On Thu, Jan 7, 2021 at 3:14 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> The CPE type of the Linux kernel is special, it should be "o", unlike
> all other packages that use "a". We therefore need to override
> <pkg>_CPE_ID_PREFIX, so that the CPE ID of the linux package matches
> with the CPE dictionary.
>
> Reported-by: Matt Weber <matthew.weber@rockwellcollins.com>
> Cc: Matt Weber <matthew.weber@rockwellcollins.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> linux/linux.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 648f6ea2a5..50d2ae3ff8 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -14,6 +14,7 @@ LINUX_LICENSE_FILES = \
> endif
> LINUX_CPE_ID_VENDOR = $(LINUX_NAME)
> LINUX_CPE_ID_NAME = $(LINUX_NAME)_kernel
> +LINUX_CPE_ID_PREFIX = cpe:2.3:o
>
Tested-by: Matt Weber <matthew.weber@rockwellcollins.com>
next prev parent reply other threads:[~2021-01-07 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 21:13 [Buildroot] [PATCH] linux: indicate proper CPE prefix Thomas Petazzoni
2021-01-07 21:13 ` [Buildroot] [PATCH] support/scripts/pkg-stats: properly handle host packages with -c option Thomas Petazzoni
2021-01-07 21:27 ` Matthew Weber
2021-01-07 21:32 ` Yann E. MORIN
2021-01-07 21:34 ` Thomas Petazzoni
2021-01-08 21:37 ` Yann E. MORIN
2021-01-11 21:25 ` Arnout Vandecappelle
2021-01-07 21:26 ` Matthew Weber [this message]
2021-01-09 16:06 ` [Buildroot] [PATCH] linux: indicate proper CPE prefix Yann E. MORIN
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='CANQCQpZ6Z_YGkCUWLT+gHz9=LRFKD8L+cvJcWQMp53v1KA3smg@mail.gmail.com' \
--to=matthew.weber@collins.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.