From: Mark H Weaver <mhw@netris.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 47028@debbugs.gnu.org
Subject: bug#47028: Discourage single-character package names
Date: Tue, 09 Mar 2021 19:44:52 -0500 [thread overview]
Message-ID: <87tupjhm5c.fsf@netris.org> (raw)
In-Reply-To: <87eegom2gk.fsf@nckx>
Hi Tobias,
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Mark H Weaver 写道:
>> 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.
>
> I completely agree (in fact I can't compel myself to find
> excusable exceptions), but this wasn't explicitly documented
> anywhere I looked.
We have one notable exception in Guix: "r", which is "grandfathered in"
so-to-speak, but perhaps it would have been excusable anyway, given its
prominence and its large number of related packages "r-*".
I fully support your proposal to talk about single-character names in
the manual, and also to check for them in the linter, but perhaps "r"
should be whitelisted.
Thank you!
Mark
next prev parent reply other threads:[~2021-03-10 0:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h7lkj3pt.fsf@netris.org>
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 ` Mark H Weaver [this message]
2021-03-10 11:28 ` bug#47028: Discourage single-character " 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
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=87tupjhm5c.fsf@netris.org \
--to=mhw@netris.org \
--cc=47028@debbugs.gnu.org \
--cc=me@tobias.gr \
/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).