unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Should guix track package aliases?
Date: Thu, 28 May 2020 18:27:09 +0200	[thread overview]
Message-ID: <87sgfk9g9u.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ3XhJfwP08ZY9=U2c_M9Gwk4SKe_GXTJMryGPN0b=phTQ@mail.gmail.com> (zimoun's message of "Sun, 10 May 2020 14:53:36 +0200")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> On Sun, 10 May 2020 at 12:08, Vincent Legoll <vincent.legoll@gmail.com> wrote:
>
>> Used googl often being used to approximate it, crudely but effectively.
>
> The big question is how to build such database.
> Wikidata?

There’s also the Common Platform Enumeration (CPE), the thing used to
refer to software in the CVE database.

Some of our packages have a ‘cpe-name’ property giving, well, their CPE
name so that ‘guix lint -c cve’ can do the right thing.

I wonder how <https://repology.org/> matches package names among distros
though.

Ludo’.


      reply	other threads:[~2020-05-28 16:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 20:18 Should guix track package aliases? Josh Marshall
2020-05-10  9:10 ` Nikita Gillmann
2020-05-10  9:57 ` zimoun
2020-05-10 12:13   ` Julien Lepiller
2020-05-10 13:33     ` zimoun
2020-05-10 18:16       ` Josh Marshall
2020-05-24 19:25         ` Josh Marshall
2020-05-25 10:41           ` zimoun
2020-05-25 11:57             ` Josh Marshall
2020-05-25 12:04               ` Nicolò Balzarotti
2020-05-25 14:20                 ` Josh Marshall
2020-05-25 21:57                   ` Vincent Legoll
2020-05-25 22:30                     ` Josh Marshall
2020-05-25 23:14                       ` zimoun
2020-05-25 23:19                         ` Josh Marshall
2020-05-10 10:08 ` Vincent Legoll
2020-05-10 12:53   ` zimoun
2020-05-28 16:27     ` Ludovic Courtès [this message]

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=87sgfk9g9u.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@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. 
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).