unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server.
Date: Tue, 26 Mar 2019 15:20:01 +0100	[thread overview]
Message-ID: <87lg11iupa.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87zhph1y9s.fsf@nckx>

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

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

> Pierre,
>
> guix-commits@gnu.org wrote:
>> gnu: wesnoth-server: Rename package to 
>> the-battle-for-wesnoth-server.
>
> My fault for totally missing the review window, but could we at 
> least drop the articles from the-long-package-names before they 
> become too widespread?  (I'll defer to you on l-abbaye, tho'.)

In this case, "battle for wesnoth" sounds good too I think.

For some titles however, I think it would not make much sense to remove
the leading article, e.g. "The Witcher", "The Fall", "The Sims", etc.
(Well, none of those examples are free software.)

If we want a consistent rule, that would mean we stick to the official
names I think.  But maybe we don't need to be this consistent.

Finally, I think long names are not problematic in practice: we have
package completion from the shell, with Geiser, Emacs-Guix.el and Helm
System Packages.

Thoughts?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

  reply	other threads:[~2019-03-26 14:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190326131842.7363.84034@vcs0.savannah.gnu.org>
     [not found] ` <20190326131845.1B177209E3@vcs0.savannah.gnu.org>
2019-03-26 14:54   ` 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server Tobias Geerinckx-Rice
2019-03-26 14:20     ` Pierre Neidhardt [this message]
2019-03-26 15:18     ` Ricardo Wurmus
2019-03-26 15:32       ` Pierre Neidhardt
2019-03-26 17:53         ` Andreas Enge
2019-03-26 18:25           ` Pierre Neidhardt
2019-03-27 11:11           ` Ludovic Courtès
2019-03-27 11:36             ` Pierre Neidhardt
     [not found] ` <20190326131844.C73EC209E3@vcs0.savannah.gnu.org>
2019-03-27 11:07   ` 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth Ludovic Courtès
2019-03-27 11:46     ` Pierre Neidhardt
2019-03-27 13:20       ` swedebugia
2019-03-27 15:00         ` Ricardo Wurmus
2019-03-27 16:42           ` Pierre Neidhardt
2019-03-28  7:59             ` Ricardo Wurmus
2019-03-28  8:09               ` Pierre Neidhardt
2019-03-29 13:27           ` swedebugia
2019-03-27 15:15         ` Ludovic Courtès
2019-03-27 18:34         ` Tobias Geerinckx-Rice
2019-03-27 18:26           ` Pierre Neidhardt
2019-03-27 18:44             ` Daniel Jiang
2019-03-27 21:15             ` Tobias Geerinckx-Rice
2019-03-28  8:17               ` Pierre Neidhardt
2019-03-29 14:02                 ` Tobias Geerinckx-Rice
2019-03-29 15:16                   ` Andreas Enge
2019-03-29 16:42                     ` Naming, hacking, and policies Ludovic Courtès
2019-03-29 19:23                       ` Ricardo Wurmus
2019-03-31 16:33                         ` Ludovic Courtès
2019-03-30 13:54                       ` sirgazil
2019-03-31 16:37                         ` Ludovic Courtès
2019-03-31 18:03                           ` sirgazil
2019-03-31 20:31                             ` Ludovic Courtès
2019-03-31 22:59                               ` sirgazil
2019-04-01  0:07                               ` Tobias Geerinckx-Rice
2019-03-29 19:57                     ` 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth swedebugia
2019-03-27 15:13       ` Ludovic Courtès
2019-03-27 16:25         ` Pierre Neidhardt

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=87lg11iupa.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mail@ambrevar.xyz \
    --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).