Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Christian Hitz <christian@klarinett.li>
Cc: Julien Corjon <corjon.j@ecagroup.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Christian Hitz <christian.hitz@bbv.ch>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/qt5/qt5base: add QT5BASE_CPE_ID_VENDOR and QT5BASE_CPE_ID_PRODUCT
Date: Sun, 21 Jan 2024 00:01:20 +0100	[thread overview]
Message-ID: <ZaxQwEvl-DSqswqA@landeda> (raw)
In-Reply-To: <20240110170759.3966933-1-christian@klarinett.li>

Christian, All,

On 2024-01-10 18:07 +0100, Christian Hitz via buildroot spake thusly:
> From: Christian Hitz <christian.hitz@bbv.ch>
> 
> cpe:2.3:a:qt:qt:5.15.8:*:*:*:*:*:*:* is a valid CPE identifier for this
> package:
> 
>   https://nvd.nist.gov/products/cpe/detail/3A753A6D-0AFE-4E62-9C2F-58C8B630830C
> 
> Signed-off-by: Christian Hitz <christian.hitz@bbv.ch>

Applied to master, thanks.

We probably want to have this defined in all qt5 packages, too. Could
you send a followup patch doing so?

Regards,
Yann E. MORIN.

> ---
>  package/qt5/qt5base/qt5base.mk | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/package/qt5/qt5base/qt5base.mk b/package/qt5/qt5base/qt5base.mk
> index cc29f5523f..91891a2ec2 100644
> --- a/package/qt5/qt5base/qt5base.mk
> +++ b/package/qt5/qt5base/qt5base.mk
> @@ -7,6 +7,8 @@
>  QT5BASE_VERSION = e44097b63d17ba3178a637df7fac51ddc51cb48b
>  QT5BASE_SITE = $(QT5_SITE)/qtbase/-/archive/$(QT5BASE_VERSION)
>  QT5BASE_SOURCE = qtbase-$(QT5BASE_VERSION).tar.bz2
> +QT5BASE_CPE_ID_VENDOR = qt
> +QT5BASE_CPE_ID_PRODUCT = qt
>  
>  QT5BASE_DEPENDENCIES = host-pkgconf pcre2 zlib
>  QT5BASE_INSTALL_STAGING = YES
> -- 
> 2.43.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-01-20 23:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 17:07 [Buildroot] [PATCH 1/2] package/qt5/qt5base: add QT5BASE_CPE_ID_VENDOR and QT5BASE_CPE_ID_PRODUCT Christian Hitz via buildroot
2024-01-10 17:07 ` [Buildroot] [PATCH 2/2] package/qt6/qt6base: add QT6BASE_CPE_ID_VENDOR and QT6BASE_CPE_ID_PRODUCT Christian Hitz via buildroot
2024-01-20 23:02   ` Yann E. MORIN
2024-02-03 12:11   ` Peter Korsgaard
2024-01-20 23:01 ` Yann E. MORIN [this message]
2024-02-03 12:11 ` [Buildroot] [PATCH 1/2] package/qt5/qt5base: add QT5BASE_CPE_ID_VENDOR and QT5BASE_CPE_ID_PRODUCT Peter Korsgaard

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=ZaxQwEvl-DSqswqA@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=christian.hitz@bbv.ch \
    --cc=christian@klarinett.li \
    --cc=corjon.j@ecagroup.com \
    --cc=giulio.benetti@benettiengineering.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