all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <rg@raghavgururajan.name>
To: Mark H Weaver <mhw@netris.org>, guix-devel@gnu.org
Cc: LibreMiami <packaging-guix@libremiami.org>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Opposition to new single-letter package name "t"
Date: Tue, 9 Mar 2021 00:39:01 -0500	[thread overview]
Message-ID: <7ae1c8ee-30fc-6639-5539-621c65e7fc26@raghavgururajan.name> (raw)
In-Reply-To: <87h7lkj3pt.fsf@netris.org>


[-- Attachment #1.1: Type: text/plain, Size: 1333 bytes --]

Hi Mark!

> Yesterday, an obscure package called "t" was added to Guix.  We should
> reject such short package names in Guix unless there's a very compelling
> reason to keep them.
> 
> The problem with single-letter package names is that the probability of
> collisions is far too high.  Due to the so-called "birthday paradox", it
> only takes 5 such package names before the probability of a collision
> gets close to 50%.  Given this, it's an act of extraordinary hubris to
> claim a single-letter name for one's package.
> 
> We've already had at least one collision involving 2-letter names.  It
> takes 26 such names before the probability of collision reaches ~50%.  A
> few years ago, someone wrote a tool based on Guile for "programmatic
> computer-aided design" and called it "Ao".  It turns out that name is
> already taken by a cross platform audio library which is in Guix.
> 
> We have precedent for renaming single-letter package names in Guix.  We
> have already changed "s" to "s-shell", and "v" to "vlang".  Let's choose
> a longer name for "t".  Here's the package definition:

Makes complete sense. Thanks for bringing it to our attention. :-)

> Any suggestions for a longer name?  Maybe "t-organizer" or
> "t-todo-list-manager"?

How about t-cli?

@Jorge WDYT?

Regards,
RG.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2021-03-09  5:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  5:27 Opposition to new single-letter package name "t" Mark H Weaver
2021-03-09  5:39 ` Raghav Gururajan [this message]
2021-03-09  5:47 ` jgart
2021-03-09  6:08   ` Raghav Gururajan
2021-03-09  9:35     ` Leo Prikler
2021-03-09 11:38     ` Tobias Geerinckx-Rice
2021-03-09 11:40       ` Julien Lepiller
2021-03-09 13:09         ` Ricardo Wurmus
2021-03-09 12:40       ` Raghav Gururajan
2021-03-09 18:12         ` Nicolas Goaziou
2021-03-10  0:16           ` Mark H Weaver
2021-03-09 13:32       ` Search improvements (Was: Opposition to new single-letter package name "t") Taylan Kammer
2021-03-09 15:12         ` zimoun
2021-03-09 16:18         ` Tobias Geerinckx-Rice
2021-03-09 18:37           ` zimoun
2021-03-09 21:39 ` bug#47028: Discourage single-character package names Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-09 21:41   ` bug#47028: [PATCH 1/2] doc: Discourage ambiguous " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-09 21:41     ` bug#47028: [PATCH 2/2] lint: Warn about single-character " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-26  8:26       ` zimoun
2021-04-01  8:51         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-04-01 20:41         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-09 21:51     ` bug#47028: [PATCH 1/2] doc: Discourage ambiguous " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-10  0:44   ` bug#47028: Discourage single-character " Mark H Weaver
2021-03-10 11:28     ` Ludovic Courtès
2021-03-10 13:04     ` zimoun
2021-04-01  8:57   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix

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=7ae1c8ee-30fc-6639-5539-621c65e7fc26@raghavgururajan.name \
    --to=rg@raghavgururajan.name \
    --cc=guix-devel@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=mhw@netris.org \
    --cc=packaging-guix@libremiami.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.