From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 31298@debbugs.gnu.org
Subject: [bug#31298] [PATCH 2/2] gnu: Add yubico-piv-tool.
Date: Mon, 30 Apr 2018 22:57:27 +0200 [thread overview]
Message-ID: <87efiwv2dk.fsf@gnu.org> (raw)
In-Reply-To: <20180428110241.18273-2-cmmarusich@gmail.com> (Chris Marusich's message of "Sat, 28 Apr 2018 04:02:41 -0700")
Chris Marusich <cmmarusich@gmail.com> skribis:
> * gnu/packages/security-token.scm (yubico-piv-tool): New variable.
LGTM!
> + (home-page "https://developers.yubico.com/yubico-piv-tool/")
> + (synopsis "Interact with the PIV application on a YubiKey")
> + (description
> + "The Yubico PIV tool is used for interacting with the Privilege and
> +Identification Card (PIV) application on a YubiKey. With it you may generate
> +keys on the device, import keys and certificates, create certificate requests,
> +and other operations. It includes a library and a command-line tool.")
> + ;; The file ykcs11/pkcs11.h also declares an additional, very short free
> + ;; license for that one file. Please see it for details. The files in
> + ;; the m4 directory are licensed under either a similarly terse free
> + ;; license or gpl2+. The vast majority of files are licensed under bsd-2.
> + (license license:bsd-2)))
I think you can omit the bit about the m4/ directory since it’s pretty
much the same story in many packages.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-04-30 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 10:57 [bug#31298] [PATCH 0/2] Add some packages related to security tokens Chris Marusich
2018-04-28 11:02 ` [bug#31298] [PATCH 1/2] gnu: Add opensc Chris Marusich
2018-04-28 11:02 ` [bug#31298] [PATCH 2/2] gnu: Add yubico-piv-tool Chris Marusich
2018-04-30 20:57 ` Ludovic Courtès [this message]
2018-05-02 5:49 ` bug#31298: " Chris Marusich
2018-04-30 20:56 ` [bug#31298] [PATCH 1/2] gnu: Add opensc Ludovic Courtès
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=87efiwv2dk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31298@debbugs.gnu.org \
--cc=cmmarusich@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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.