All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@buildroot.org
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Johan Oudinet <johan.oudinet@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/forge: add FORGE_CPE_ID_VENDOR
Date: Sat, 24 Sep 2022 22:51:48 +0200	[thread overview]
Message-ID: <20220924205148.20621-1-fontaine.fabrice@gmail.com> (raw)

cpe:2.3:a:digitalbazaar:forge is a valid CPE identifier for this package:

  https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe%3A2.3%3Aa%3Adigitalbazaar%3Aforge

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
 package/forge/forge.mk | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/forge/forge.mk b/package/forge/forge.mk
index 9a811b4929..0b81295a15 100644
--- a/package/forge/forge.mk
+++ b/package/forge/forge.mk
@@ -9,6 +9,7 @@ FORGE_SITE = https://registry.npmjs.org/node-forge/-
 FORGE_SOURCE = node-forge-$(FORGE_VERSION).tgz
 FORGE_LICENSE = BSD-3-Clause, GPL-2.0, vendored dependencies licenses probably not listed
 FORGE_LICENSE_FILES = LICENSE
+FORGE_CPE_ID_VENDOR = digitalbazaar
 
 # Install .min.js as .js
 define FORGE_INSTALL_TARGET_CMDS
-- 
2.35.1

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

             reply	other threads:[~2022-09-24 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 20:51 Fabrice Fontaine [this message]
2022-09-24 21:40 ` [Buildroot] [PATCH 1/1] package/forge: add FORGE_CPE_ID_VENDOR Thomas Petazzoni

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=20220924205148.20621-1-fontaine.fabrice@gmail.com \
    --to=fontaine.fabrice@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=johan.oudinet@gmail.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 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.