From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: Font package naming convention
Date: Thu, 30 Oct 2014 23:54:55 +0100 [thread overview]
Message-ID: <8761f1i2ww.fsf@gnu.org> (raw)
In-Reply-To: <20141030173207.GA17993@debian.eduroam.u-bordeaux.fr> (Andreas Enge's message of "Thu, 30 Oct 2014 18:32:07 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> On Thu, Oct 30, 2014 at 06:20:46PM +0100, Ludovic Courtès wrote:
>> There’s no documented convention (yet), so it’s not a mistake strictly
>> speaking. :-)
>
> We have a convention for package names, including fonts;
You mean the convention of choosing the upstream name, right?
> But we could choose another one close to the naming of python and perl modules
> if enough people wish to have special rules for fonts.
Yes, it would make sense to take this route for fonts and have something
akin to what Alex just suggested, because the upstream name is only
occasionally going match one’s expectations.
How does that sound?
Ludo’.
next prev parent reply other threads:[~2014-10-31 15:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 6:53 [PATCH 2/2] gnu: Add 'ttf-liberation' Alex Kost
2014-10-28 8:10 ` Ludovic Courtès
2014-10-29 22:16 ` Andreas Enge
2014-10-30 7:27 ` Alex Kost
2014-10-30 7:56 ` Andreas Enge
2014-10-30 12:52 ` Alex Kost
2014-10-30 13:36 ` Andreas Enge
2014-10-30 18:55 ` Alex Kost
2014-10-30 17:20 ` Font package naming convention Ludovic Courtès
2014-10-30 17:32 ` Andreas Enge
2014-10-30 22:54 ` Ludovic Courtès [this message]
2014-10-30 18:55 ` Alex Kost
[not found] ` <20141030191743.GB19999@debian.eduroam.u-bordeaux.fr>
2014-10-30 22:02 ` Alex Kost
2014-10-31 17:58 ` Andreas Enge
2014-10-31 18:00 ` Andreas Enge
2014-10-31 21:30 ` Ludovic Courtès
2014-11-01 9:52 ` Andreas Enge
2014-11-02 17:18 ` Ludovic Courtès
2014-11-02 17:49 ` Andreas Enge
2014-11-03 8:53 ` Ludovic Courtès
2014-11-03 9:30 ` Andreas Enge
2014-11-03 13:36 ` Alex Kost
2014-11-03 20:28 ` Ludovic Courtès
2014-11-19 9:01 ` Ludovic Courtès
2014-11-19 10:22 ` Andreas Enge
2014-11-20 7:09 ` Alex Kost
2014-11-23 20:13 ` [PATCH] gnu: Add 'font-liberation' Alex Kost
2014-11-24 14:12 ` Ludovic Courtès
2014-11-01 9:36 ` Font package naming convention Alex Kost
2014-11-01 9:45 ` Andreas Enge
2014-11-01 10:55 ` Alex Kost
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=8761f1i2ww.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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).