unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/2] New pinentries
Date: Thu, 28 Apr 2016 04:59:43 +0300	[thread overview]
Message-ID: <20160428015943.GA17619@debian-netbook> (raw)
In-Reply-To: <20160427170549.GB13823@jasmine>

[-- Attachment #1: Type: text/plain, Size: 2669 bytes --]

On Wed, Apr 27, 2016 at 01:05:49PM -0400, Leo Famulari wrote:
> On Wed, Apr 27, 2016 at 12:00:59AM +0300, Efraim Flashner wrote:
> > On Tue, Apr 26, 2016 at 01:13:09PM -0400, Leo Famulari wrote:
> > > On Tue, Apr 26, 2016 at 04:33:16PM +0200, Ricardo Wurmus wrote:
> > > > 
> > > > Hi Efraim,
> > > > 
> > > > > On a whim I removed gtk2 and glib from pinentry and the size of the closure
> > > > > dropped from 700 MiB to 100 MiB. While I was at it I built a version with
> > > > > qt5, if someone wanted it to match a future kde/qt-based desktop. I couldn't
> > > > > get a gtk3 version building, but I didn't try too hard.
> > > > >
> > > > > Efraim Flashner (2):
> > > > >   gnu: Add minimal pinentry.
> > > > >   gnu: Add pinentry-qt.
> > > > >
> > > > >  gnu/packages/gnupg.scm | 34 +++++++++++++++++++++++++++++-----
> > > > >  1 file changed, 29 insertions(+), 5 deletions(-)
> > > > 
> > > > These both look good to me.  I think our policy requires to split the
> > > > first patch in two, one to reduce pinentry, the other to add
> > > > pinentry-gtk2, but I’m not sure.
> > > 
> > > I had the same thought, but it would mean we have a commit in our
> > > history where we *don't* have the GTK pinentry. I think we should avoid
> > > that.
> > 
> > I thought about that too. With the patches I have we'll have people who
> > have pinentry installed who suddenly find that they don't have a gtk-2
> > pop-up anymore. I suppose another option would be to leave pinentry its
> > name and call the curses-only pinentry pinentry-curses or
> > pinentry-minimal or pinentry-tty.
> 
> Good point. That would be a poor experience for our users.
> 
> Although I would prefer if the console-based pinentry was called
> pinentry, I'd rather not change the meaning of the existing variable for
> a program that is so important.
> 
> So, pinentry-tty or pinentry-curses makes sense to me.

I'll double-check the descriptions to add that the gtk/qt versions also
have the curses interface, don't want people to think they need
pinentry-curses and pinentry-gtk.

> 
> > In terms of the commit order, maybe one to rename pinentry->pinentry-gtk
> > and a second to add pinentry?
> 
> Since I think it's best if users of 'pinentry' don't experience any
> disruption, perhaps we could add a variable pinentry-gtk that inherits
> from pinentry? Maybe eventually we could deprecate 'pinentry'.

I like that idea.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-04-28  1:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 14:03 [PATCH 0/2] New pinentries Efraim Flashner
2016-04-26 14:03 ` [PATCH 1/2] gnu: Add minimal pinentry Efraim Flashner
2016-04-26 17:14   ` Leo Famulari
2016-04-26 21:02     ` Efraim Flashner
2016-04-27 17:06       ` Leo Famulari
2016-04-26 14:03 ` [PATCH 2/2] gnu: Add pinentry-qt Efraim Flashner
2016-04-26 17:15   ` Leo Famulari
2016-04-26 14:33 ` [PATCH 0/2] New pinentries Ricardo Wurmus
2016-04-26 17:13   ` Leo Famulari
2016-04-26 21:00     ` Efraim Flashner
2016-04-27 17:05       ` Leo Famulari
2016-04-28  1:59         ` Efraim Flashner [this message]
2016-04-28  2:49           ` Efraim Flashner
2016-04-29  5:42             ` Leo Famulari

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=20160428015943.GA17619@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).