unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Why ban underscores?
Date: Sat, 17 Apr 2021 17:54:12 +0200	[thread overview]
Message-ID: <874kg4uct7.fsf@gnu.org> (raw)
In-Reply-To: <87v991vkpi.fsf@nckx> (Tobias Geerinckx-Rice's message of "Sun, 04 Apr 2021 22:49:45 +0200")

Hi Tobias,

Tobias Geerinckx-Rice <me@tobias.gr> skribis:

> I was surprised by this commit:
>
> commit 426ade6c8bdab243da719e369a887284368179bb (upstream/master)
> Author: Xinglu Chen <public@yoctocell.xyz>
>
>     import: go: Replace underscores with hyphens in package names.
>
>     As per section '16.4.2 Package Naming' in the manual, use 
>     hypens
>     [sic] instead of underscores in package names.
>
>     * guix/import/go.scm (go-module->guix-package-name): Replace
>     underscores with hyphens.
>
>     Signed-off-by: Leo Famulari <leo@famulari.name>
>
>
> Indeed, underscores were explicitly banned in 2014 (commit 
> 25083588).  Why?

It’s a convention.  As Mark wrote, it’s mostly for the sake of
consistency.

> Where's the advantage in renaming the following packages from 
> their canonical names?

These package names didn’t follow the convention, so the change would
bring them back in line.  The “advantage” is just consistent naming and
following the rule of least surprise.

Now, renames should only be performed with proper ‘deprecated-package’
definitions in place so users aren’t caught by surprise.

I hope that makes sense!

Ludo’.


      parent reply	other threads:[~2021-04-17 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04 20:49 Why ban underscores? Tobias Geerinckx-Rice
2021-04-04 20:54 ` Vincent Legoll
2021-04-04 21:05 ` Mark H Weaver
2021-04-05  1:05   ` Bengt Richter
2021-04-17 15:54 ` Ludovic Courtès [this message]

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=874kg4uct7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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).