[Pkg-fonts-devel] defoma, fontconfig and oldish font packages

Paul Wise pabs at debian.org
Tue May 21 08:55:17 UTC 2013

On Tue, May 21, 2013 at 4:32 PM, Thorsten Glaser wrote:

> I’ve set fontforge on hold for now since it started
> conflicting with defoma, which is a bit irritating
> because I had, for the business, to locally package
> a font we purchased, so we can use/deploy it on all
> company desktops. I’ve originally done so for lenny
> and hardy, so the defoma use was a requirement, and
> I just used that package on wheezy/sid too.

defoma is dead and isn't coming back since it was replaced by
fontconfig, which is cross-distro.

> Why does fontforge Conflicts: defoma now?

There is no need for it to do so now and there never was such a need,
I'm not sure why that got added.

> If I absolutely have to repackage that font, which
> Debian font source package(s) would you recommend
> me to use as example/template? The font in question
> (ttf-museo-sans) originally came as a bunch of OTF
> files, but we had the Foundry give us a TTF variant
> where the weights were identified differently, since
> OOo had trouble with the OTF ones; I don’t know how
> far along the OTF support in recent Debian is, so I’m
> at a bit of loss what to do now (the current/old .deb
> I made ships both but only registers the TTF files
> with defoma).

With fontconfig there isn't any need to register fonts, as long as you
install them in a subdir of /usr/share/fonts. Any font package named
fonts-* should be a good example, we updated a lot of them before
wheezy was released. My advice would be to drop the defoma parts of
your package, rename it to fonts-museo-sans and rebuild. OTF support
should be pretty good these days.



More information about the Pkg-fonts-devel mailing list