From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Libre games that might be worth packaging :)
Date: Mon, 18 Mar 2019 13:39:41 +0100 [thread overview]
Message-ID: <87va0gxsoi.fsf@elephly.net> (raw)
In-Reply-To: <87mulszdt9.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Dan Frumin <dfrumin@cs.ru.nl> writes:
>
>>> Shouldn't we name this "dungeon-crawl-stone-soup"?
>>>
>>
>> Possibly, but the official packages from crawl.develz.org are called `crawl' and `crawl-tiles'.
>
> Maybe packagers use abbreviated names, often with underscores or simply
> no word separator.
>
> I think we should not follow what other packagers do, but rather what
> the _users_ expect. The full program name is much more certain to be
> known to the wider audience rather than some abbreviation that is only
> known to the set of developers / restricted community members.
This is what our packaging guidelines say:
--8<---------------cut here---------------start------------->8---
14.4.2 Package Naming
---------------------
[…]
Both [variable name and package name] […]
correspond to the lowercase conversion of the project name chosen
upstream, with underscores replaced with hyphens.
--8<---------------cut here---------------end--------------->8---
--
Ricardo
next prev parent reply other threads:[~2019-03-18 12:47 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 [this message]
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
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=87va0gxsoi.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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.