From: Pierre Neidhardt <mail@ambrevar.xyz>
To: swedebugia <swedebugia@riseup.net>, Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Libre games that might be worth packaging :)
Date: Tue, 19 Mar 2019 12:21:18 +0100 [thread overview]
Message-ID: <87r2b3w1n5.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CF9C49EF-CFFA-4DB9-AEBD-6EA48EBEC87C@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
swedebugia <swedebugia@riseup.net> writes:
> Arch seems to have this and it is used in the gui tools like pamac but not on the command line.
> We could solve this by adding a new optional field to the package record (pretty-name "Armagetron Advanced")
Does it? I could not find a mention of this in the PKGBUILD article:
https://wiki.archlinux.org/index.php/PKGBUILD#pkgname
> For the packages that lack this field I would in the gui display them like this:
> (name "aircrack-ng") -> Aircrack-ng
Actually more like
(name "aircrack-ng") -> Aircrack Ng
since hyphens are added by us. In this specific example, it does not do
the right thing.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-03-19 11:21 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
2019-03-19 11:06 ` swedebugia
2019-03-19 11:21 ` Pierre Neidhardt [this message]
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=87r2b3w1n5.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 \
--cc=swedebugia@riseup.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.