all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Libre games that might be worth packaging :)
Date: Mon, 18 Mar 2019 16:32:26 +0100	[thread overview]
Message-ID: <871s34ci5x.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87r2b4xp5t.fsf@elephly.net>

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

Ricardo Wurmus <rekado@elephly.net> writes:

> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>> It's named "armagetronad".  Shouldn't we name this
>> "armagetron-advanced"?
>
> Instead of renaming the packages (whose names follow our packaging
> guidelines) how about adding the full name of the games to the
> description?

That would not help interfaces like Emacs-Guix and Helm-System-Packages.
I think names are more important than having obsolete packages :)

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

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

  reply	other threads:[~2019-03-18 15:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 16:51 Libre games that might be worth packaging :) swedebugia
2019-03-17 18:36 ` swedebugia
2019-03-17 18:42 ` Dan Frumin
2019-03-17 18:49 ` Ricardo Wurmus
2019-03-18  7:25   ` Pierre Neidhardt
2019-03-18  9:14     ` Dan Frumin
2019-03-18 10:17       ` Pierre Neidhardt
2019-03-18 12:39         ` Ricardo Wurmus
2019-03-18 13:55     ` Ricardo Wurmus
2019-03-18 15:32       ` Pierre Neidhardt [this message]
2019-03-19 11:06         ` swedebugia
2019-03-19 11:21           ` Pierre Neidhardt
2019-03-26 13:20             ` Pierre Neidhardt
2019-03-29 11:49       ` swedebugia
2019-03-17 18:53 ` Ricardo Wurmus
2019-03-18 15:00 ` Kei Kebreau

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=871s34ci5x.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.