guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 2/2] gnu: Add 'ttf-liberation'.


From: Andreas Enge
Subject: Re: [PATCH 2/2] gnu: Add 'ttf-liberation'.
Date: Thu, 30 Oct 2014 14:36:06 +0100
User-agent: Mutt/1.5.23 (2014-03-12)

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 via email to

[Prev in Thread] Current Thread [Next in Thread]