unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: guix-devel@gnu.org
Subject: Re: Introduce a cpe-vendor package property?
Date: Sat, 26 Oct 2024 17:08:21 +0200	[thread overview]
Message-ID: <87wmhuvr4q.fsf@gnu.org> (raw)
In-Reply-To: <87msise285.fsf@ngraves.fr> (Nicolas Graves's message of "Fri, 25 Oct 2024 15:33:46 +0200")

Hi,

Nicolas Graves <ngraves@ngraves.fr> skribis:

> I was wondering about handling a cpe-vendor property to handle such
> cases, since cpe-name won't help here.

Yes, we need that.  (guix cve) currently blissfully ignores the “vendor”
part of CPE names; we can do better.

Thanks,
Ludo’.


  reply	other threads:[~2024-10-26 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 13:33 Introduce a cpe-vendor package property? Nicolas Graves
2024-10-26 15:08 ` Ludovic Courtès [this message]
2024-10-27 18:29   ` Nicolas Graves

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wmhuvr4q.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ngraves@ngraves.fr \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).