Bug 477334 - [darkgarden-fonts] Please convert to new font packaging guidelines
Summary: [darkgarden-fonts] Please convert to new font packaging guidelines
Alias: None
Product: Fedora
Classification: Fedora
Component: darkgarden-fonts
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Lyos Gemini Norezel
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F11-new-font-rules
TreeView+ depends on / blocked
Reported: 2008-12-20 17:11 UTC by Nicolas Mailhot
Modified: 2009-03-03 05:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-03-03 05:22:26 UTC
Type: ---

Attachments (Terms of Use)

Description Nicolas Mailhot 2008-12-20 17:11:37 UTC
After more than a month of consultation,
feedback and tweaking new font packaging guidelines have been approved


Package maintainers must now convert their packages in rawhide to the new templates.

The following packages have already been converted in rawhide and can
serve as examples if the templates published in the fontpackages-devel package are not clear enough:

❄ andika-fonts
❄ apanov-heuristica-fonts
❄ bitstream-vera-fonts
❄ charis-fonts
❄ dejavu-fonts
❄ ecolier-court-fonts
❄ edrip-fonts
❄ gfs-ambrosia-fonts
❄ gfs-artemisia-fonts
❄ gfs-baskerville-fonts
❄ gfs-bodoni-classic-fonts
❄ gfs-bodoni-fonts
❄ gfs-complutum-fonts
❄ gfs-didot-classic-fonts
❄ gfs-didot-fonts
❄ gfs-eustace-fonts
❄ gfs-fleischman-fonts
❄ gfs-garaldus-fonts
❄ gfs-gazis-fonts
❄ gfs-jackson-fonts
❄ gfs-neohellenic-fonts
❄ gfs-nicefore-fonts
❄ gfs-olga-fonts
❄ gfs-porson-fonts
❄ gfs-solomos-fonts
❄ gfs-theokritos-fonts
❄ stix-fonts
❄ yanone-kaffeesatz-fonts

FPC and FESCO were not consulted on splitting or renaming packages, nevertheless the new templates make it fare easier to manage subpackages, so you're strongly encouraged to split your packages along font family lines.

A mandatory rule about splitting will probably be submitted for approval before the F11 release.

Further information on fonts packaging changes will be published on fedora-fonts-bugs-list at redhat.com

Comment 1 Nicolas Mailhot 2009-01-11 15:19:07 UTC
To help packagers manage the transition to the new guidelines, we've published the following FAQ


Comment 2 Lyos Gemini Norezel 2009-01-12 16:19:29 UTC
Updates are in Koji now.

Comment 3 Nicolas Mailhot 2009-01-12 23:48:29 UTC
Some darkgarden QA

You should not need the %{_fontdir}/*.ttf line

That's the source of this build warning
warning: File listed twice: /usr/share/fonts/darkgarden/DarkGarden.ttf

Also there are simple fontconfig templates in fontpackages-devel that only require filling of your font name, so it may be a good idea to add one to your package

Comment 4 Nicolas Mailhot 2009-01-12 23:50:42 UTC
(In reply to comment #3)
> Some darkgarden QA

> Also there are simple fontconfig templates in fontpackages-devel that only
> require filling of your font name, so it may be a good idea to add one to your
> package

Forget this part, that's me needing to stop looking at spec files for a while

Comment 5 Nicolas Mailhot 2009-01-14 18:36:34 UTC
FPC approved those two additional guidelines recently, please take them into account if you need to create or update a fonts package or subpackage:

– 2009-01-14: naming

— 2009-01-06: exact splitting rules

(packagers that can drop font files and just depend on an existing font package are not impacted)

Comment 6 Nicolas Mailhot 2009-02-18 19:31:48 UTC
This is a reminder for all the packagers that still have bugs open about adapting to font packaging guidelines there is only one month left before Fedora 11 beta:

A week of this month will see the Fedora 11 mass rebuild, that will load the build farm:

As already converted packages showed it is quite possible to make mistakes during the conversion. Please make releng and QA happy and don't wait till the last minute to do your changes (avoid pre-beta panic). If possible start before the mass rebuild so we don't burn cycles on incorrect packages.

The PackageKit enhancements stated for Fedora 11 assume fonts and font-using packages are sane (basically respect packaging guidelines). It is quite possible that not-converted packages will interact with the F11 font autoinstall feature in "interesting" ways.

We don't want that

There is extensive documentation on the wiki and most of your questions have likely already been answered there. Please do read the FAQ before making more work for the support team by asking questions answered there.

Comment 7 Lyos Gemini Norezel 2009-03-03 05:22:26 UTC

Note You need to log in before you can comment on or make changes to this bug.