all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 4/6] gnu: Add gpgscm.
Date: Mon, 18 Jul 2016 14:35:54 +0200	[thread overview]
Message-ID: <87wpkjp1hx.fsf@gnu.org> (raw)
In-Reply-To: <87lh0z97jm.fsf@we.make.ritual.n0.is> (ng0@we.make.ritual.n0.is's message of "Sun, 17 Jul 2016 23:19:41 +0000")

Hello!

ng0 <ng0@we.make.ritual.n0.is> skribis:

> From 6babb18479de83bd19c44412c7957918d2c917b2 Mon Sep 17 00:00:00 2001
> From: ng0 <ng0@we.make.ritual.n0.is>
> Date: Sun, 17 Jul 2016 22:11:41 +0000
> Subject: [PATCH 4/6] gnu: Add gpgscm.
>
> * gnu/packages/gnupg.scm (gpgscm): New variable.

[...]

> +    (home-page "https://gnupg.org/")
> +    (synopsis "tinyscheme implementation used by The GNU Privacy Guard")

I’ve seen some of the discussions on IRC about gpgscm.  However, it’s
not clear to me why we should make it a separate package.  AIUI, it’s
meant as a purely GnuPG-internal tool, and as such it may evolve in
lockstep with the rest of the GnuPG code base.

So I’d be tempted to keep it internal to GnuPG, unless upstream decides
to make it a separate package (which seems unlikely; it may be come part
of libgpg-error, though.)

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2016-07-18 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-17 23:19 [PATCH 4/6] gnu: Add gpgscm ng0
2016-07-18 12:35 ` Ludovic Courtès [this message]
2016-07-18 14:10   ` ng0
2016-07-19 12:53     ` Ludovic Courtès
2016-07-18 14:13 ` ng0
2016-07-18 17:44 ` Leo Famulari
2016-07-18 22:16   ` Leo Famulari
2016-07-18 23:10     ` ng0
2016-07-19  3:58       ` Leo Famulari
2016-07-19  7:14         ` Andreas Enge

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=87wpkjp1hx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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.