[Pkg-fonts-devel] fontforge packaging update and queries

Vasudev Kamath vasudev at copyninja.info
Mon May 30 14:51:44 UTC 2016

Adam Borowski <kilobyte at angband.pl> writes:

> On Sun, May 29, 2016 at 07:10:43PM +0200, Jonas Smedegaard wrote:
>> Quoting Vasudev Kamath (2016-05-29 18:03:20)
>> > Coming to actual part. I noticed there is a fontforge-nox package 
>> > which is built bit weirdly . It does entire fontforge build process 
>> > from override_dh_strip target, by disabling X support and python 
>> > extension.
> I'd recommend building in two separate directories instead.

OK I will see how I can do that.

>> > Package description says its without X and used only for scripting. 
>> > But I wonder if any one is using this package. In most of my font 
>> > packages I directly use fontforge to build fonts from source. Does any 
>> > one else has use case for fontforge-nox?.
> For building font packages, please use fontforge-nox instead of fontforge.
> It's way lighter for buildds.  The proper way to do so is:
> Build-Depends: fontforge-nox | fontforge

Alright, noted. I think we should include this in our team policy to
build fonts from source. I know not a proper document exist as policy
but we can create one.

>> > Just to briefly say it all do we need fontforge-nox, we can simply use 
>> > fontforge from scripts. If we don't need it we should stop building 
>> > this package.
>> This check shows quite a few hits:
>>   apt-rdepends fontforge-nox
> That shows just a single hit.  I guess you meant build-rdeps, which shows
> 32.
>> Yes, we need it.
> Strictly speaking, it's "want" not "need".  The full-blown version can do
> everything -nox can, if the maintenance burden is too high dropping -nox
> is an possibility: human time is expensive, computer (buildd) time is cheap.
> But the current way is better.


More information about the Pkg-fonts-devel mailing list