all messages for Guix-related lists mirrored at yhetil.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: [PATCH 2/2] gnu: Add 'ttf-liberation'.
Date: Thu, 30 Oct 2014 14:36:06 +0100	[thread overview]
Message-ID: <20141030133606.GA7705@debian.eduroam.u-bordeaux.fr> (raw)
In-Reply-To: <8738a5g1nh.fsf@gmail.com>

On Thu, Oct 30, 2014 at 03:52:50PM +0300, Alex Kost wrote:
> I don't understand why you call it a mistake.  It's just a package name
> used by some distributions (and I think it's a good name).  Is there a
> convention to use “…-fonts-ttf” in Guix?

It may be a good name, but the Guix convention is to not choose names, but
to simply use the upstream name. This is described in the packaging
guidelines, section 6.5.2 of the documentation:
"Both are usually the same and correspond to the lowercase conversion of
the project name chosen upstream, with underscores replaced with hyphens".
So liberation-fonts-ttf-2.00.1.tar.gz becomes liberation-fonts-ttf.
(Admittedly "project name" is a bit vague; it means "tarball name", the
aim is not to call all packages of the x.org system x-org, so that
only one of them could be installed ;-)).

And dejavu-fonts-ttf-2.34.tar.bz2 should become dejavu-fonts-ttf. 

And font-adobe-100dpi-1.0.3.tar.bz2 should have become font-adobe-100dpi,
but apparently I made a mistake and called it font-adobe100dpi.
Another mistake to correct. In particular, it is not called
adobe-100dpi-fonts-pcf.


We have different naming rules for python and perl modules. We could also
agree on different naming rules for fonts. But they would need to be
consistent, in particular over different font formats, and mechanically
applicable. Personally, I do not see a pressing need.

Andreas

  reply	other threads:[~2014-10-31 15:48 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141030133606.GA7705@debian.eduroam.u-bordeaux.fr \
    --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 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.