Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Clément Ramirez via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: "Clément Ramirez" <clement.ramirez@bootlin.com>
Subject: [Buildroot] [PATCH 1/1] package/composer: add COMPOSER_CPE_ID_VENDOR
Date: Wed,  9 Aug 2023 09:56:23 +0200	[thread overview]
Message-ID: <20230809075623.306089-1-clement.ramirez@bootlin.com> (raw)

cpe:2.3:a:getcomposer:composer is a valid identifier for
this package:
https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=getcomposer

Signed-off-by: Clément Ramirez <clement.ramirez@bootlin.com>
---
 package/composer/composer.mk | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/composer/composer.mk b/package/composer/composer.mk
index fde5b48951..9bfabc28af 100644
--- a/package/composer/composer.mk
+++ b/package/composer/composer.mk
@@ -13,6 +13,7 @@ BASE_SITE = https://getcomposer.org/download/$(COMPOSER_VERSION)/composer.phar
 COMPOSER_SITE = $(BASE_SITE)?n=f/$(COMPOSER_SOURCE)
 COMPOSER_LICENSE = MIT
 COMPOSER_LICENSE_FILES = LICENSE
+COMPOSER_CPE_ID_VENDOR = getcomposer
 
 HOST_COMPOSER_DEPENDENCIES = host-php
 HOST_COMPOSER_EXTRACT_DEPENDENCIES = host-php
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-08-09  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09  7:56 Clément Ramirez via buildroot [this message]
2023-08-09 17:40 ` [Buildroot] [PATCH 1/1] package/composer: add COMPOSER_CPE_ID_VENDOR Thomas Petazzoni via buildroot

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=20230809075623.306089-1-clement.ramirez@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=clement.ramirez@bootlin.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