all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: 58386-done@debbugs.gnu.org, 58340-done@debbugs.gnu.org
Subject: bug#58340: [PATCH v2] gnu: Add passage.
Date: Wed, 19 Oct 2022 19:17:33 +0200	[thread overview]
Message-ID: <87h6zzbo14.fsf@nckx> (raw)
In-Reply-To: <87y1tmujj2.fsf@ngraves.fr>

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

Hi Nicolas,

Nicolas Graves 写道:
> Just as a reminder, this patch cannot be merged before 58340.

Thanks, I realised that after I sent it.  I'll treat (and close) 
them as one bug for this reply.

I've pushed all 3 patches as 
ac553ba68e535810085dd838e48e4fa6ac553e67 et al with the following 
mods:

> * gnu/packages/password-utils.scm (passage): New variable.

I fixed up the commit message to match the name, and addressed the 
following ‘guix lint’ warnings:

  pass-age@1.7.4a0: no article allowed at the beginning of the 
  synopsis
  age@1.0.0: sentences in description should be followed by two 
  spaces

Whilst there, I turned @code{age-encryption.org/v1} into a full 
@url{}, and fixed up upstream's ‘config’ & ‘UNIX’ slang.

> * gnu/packages/golang.scm
>   (age): New variable.
>   (go-filippo-io-cmd-age): New variable.
>   (go-filippo-io-cmd-age-keygen): New variable.
  ^^
Our changelogs are never indented, you'd write:

> * gnu/packages/golang.scm (age, go-filippo-io-cmd-age)
> (go-filippo-io-cmd-age-keygen): New variables.

…but in this case, I was bold and removed the two 
go-filippo-io-cmd-age* packages completely.  I moved ‘age’ to (gnu 
packages password-utils).

The partial recursion in the go-* variants made me nervous (and 
would probably prevent the move, although I didn't try).

If these variants are needed for something, it's not pass-age, and 
we can review them separately if/when needed.  Is that acceptable?

> I would think that choices need to be made

Princip(al)ly: the choice to reuse an existing package name was 
FiloSottile's, for the sake of a pun.  Much as I like bad puns, I 
think that's rather rude.  It's not hard to search for free 
package names, e.g., [0].

> that this one would not annoy a lot.

Technically: it would silently replace users' games with some 
encryption tool.  That's problematic even if those users are few.

Similarly: had the game been added after this ‘passage’, I would 
have grumpily agreed to ‘passage-game’ :-)  But it wasn't.

But: I think your ’pass-age’ solution is perfect.  Thanks! 
FiloSottile should consider it.

Kind regards,

T G-R

[0]: https://repology.org/project/passage/versions


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

  reply	other threads:[~2022-10-19 19:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 22:42 [bug#58386] Age encryption : passage Nicolas Graves via Guix-patches via
2022-10-08 22:44 ` [bug#58386] [PATCH 1/2] gnu: passage: Rename package to passage-game Nicolas Graves via Guix-patches via
2022-10-08 22:44   ` [bug#58386] [PATCH 2/2] gnu: Add passage Nicolas Graves via Guix-patches via
2022-10-08 23:05     ` Tobias Geerinckx-Rice via Guix-patches via
2022-10-11 21:39       ` [bug#58386] [PATCH v2] " Nicolas Graves via Guix-patches via
2022-10-19 17:17         ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-10-19 19:49           ` [bug#58340] bug#58386: " Tobias Geerinckx-Rice via Guix-patches via
2022-10-22  7:51             ` Nicolas Graves via Guix-patches via
2022-10-19 19:54         ` bug#58457: " Tobias Geerinckx-Rice via Guix-patches via

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=87h6zzbo14.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=58340-done@debbugs.gnu.org \
    --cc=58386-done@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=ngraves@ngraves.fr \
    /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.