From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: "g33k0b0y ." <g33k0b0y@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: GnuPG in Guix
Date: Thu, 26 Feb 2015 11:01:29 +0100 [thread overview]
Message-ID: <87bnkh56va.fsf@taylan.uni.cx> (raw)
In-Reply-To: <CAB102fauOHxH3aKUfJ0sBbvuB8XqaMNc7NhXxNQ7sG90tE0oXQ@mail.gmail.com> (g33k0b0y .'s message of "Thu, 26 Feb 2015 15:46:05 +1100")
"g33k0b0y ." <g33k0b0y@gmail.com> writes:
> It seems that Guix can install multiple versions of GPG. It names the
> 1.4.18 version as gpg, and the 2.0.26 version as gpg2.
>
> There is a problem, however.
>
> By default Guix installs the highest version, which is 2.0.26.
> However, an potential newbie could try calling it through bash as gpg.
> This won't work, as it hasn't installed gpg version 1.4.18 and
> therefore is expecting only gpg2 as its command. This is not made
> clear to the user.
>
> If I am an inexperienced user and install gnupg, from my previous
> experience with other distros, (Trisquel, gNewSense) I would expect to
> use gpg to call it. Imagine my surprise when bash says command not
> found! I am never told to use gpg2 as the command, nor would I think
> of it.
>
> How can we improve this?
My first instinct when a command I expect to be found isn't found is to
try to tab-complete it in some way, because it happens occasionally that
a CLI command has a different name than one would expect, indeed often
because of such version issues.
So I'd have thought it's fine, and people should get used to it; GPG
isn't unique or rare in this regard. I think Debian does the same too.
Taylan
next prev parent reply other threads:[~2015-02-26 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 4:46 GnuPG in Guix g33k0b0y .
2015-02-26 8:21 ` Ricardo Wurmus
2015-02-26 17:16 ` Ludovic Courtès
2015-02-26 18:14 ` Andreas Enge
2015-02-26 10:01 ` Taylan Ulrich Bayırlı/Kammer [this message]
2015-02-26 15:59 ` Mark H Weaver
2015-02-26 16:05 ` Andreas Enge
2015-02-26 18:13 ` Mark H Weaver
2015-02-26 16:09 ` 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=87bnkh56va.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=g33k0b0y@gmail.com \
--cc=guix-devel@gnu.org \
/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.