unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Font package naming convention
Date: Sat, 1 Nov 2014 10:45:52 +0100	[thread overview]
Message-ID: <20141101094552.GA30939@debian> (raw)
In-Reply-To: <87fve3s1nl.fsf@gmail.com>

Alex,

On Sat, Nov 01, 2014 at 12:36:30PM +0300, Alex Kost wrote:
> I think the majority should decide.  So if the most of guix people think
> that it should be named "bar", then let it be so.

for this we would need an "infrastructure": a social contract, a voting
system and what else not, which seems a bit like overkill to decide on package
names. Even debian does not hold general resolutions for the names of their
packages...

> However, I still think that having the following packages would be the
> best:
>   ttf-bitstream-vera
>   ttf-dejavu
>   ttf-freefont
>   ttf-liberation
>   ttf-symbola

Okay, could you please formulate your suggestion into a rule that we could
follow for other font packages than these five?

Andreas

  reply	other threads:[~2014-11-01  9:46 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
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 [this message]
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=20141101094552.GA30939@debian \
    --to=andreas@enge.fr \
    --cc=alezost@gmail.com \
    --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).