[Pkg-fonts-devel] Bug#609094: Bug#609094: Bug#609094: fontforge: Fails to build ttf-dejavu
zinosat at gmail.com
Tue Jan 18 12:11:04 UTC 2011
Well, you could apply this thought to any program; you just want use
it and sometimes you get some gcc bugs
Il giorno 18/gen/2011, alle ore 12:26, Khaled Hosny
<khaledhosny at eglug.org> ha scritto:
> On Tue, Jan 18, 2011 at 12:07:20PM +0100, Julien Cristau wrote:
>> On Thu, Jan 6, 2011 at 21:27:11 +0200, Khaled Hosny wrote:
>>> On Wed, Jan 05, 2011 at 08:13:28PM -0800, Daniel Schepler wrote:
>>>> Package: fontforge
>>>> Version: 0.0.20100501-4
>>>> Severity: serious
>>> Bugs like this make wounder if it is wise for distributions to build
>>> fonts from source instead of just using upstream supplied font files.
>>> I mean, what is the benefit from building from source? I, as a font
>>> author, I can see many possible problems with no obvious benefit.
>> If we didn't build from source, we wouldn't catch bugs like this.
> Which is good thing?
> I mean the purpose of font packages is to be used, not catch FontForge
> bugs, and there are FontForge bugs that can pass unnoticed at build
> See also:
> for a non-bug that just screwed the font up. Another reason why it is
> not, yet, a good idea to build fonts on your own.
> (BTW, it is already known that there are places in the code that don't
> go well with doubles and crashes like this have been reported upstream
> already, still there are certain tasks that can't be reliably done
> without building fontforge to use doubles).
> Khaled Hosny
> Arabic localiser and member of Arabeyes.org team
> Free font developer
> Pkg-fonts-devel mailing list
> Pkg-fonts-devel at lists.alioth.debian.org
More information about the Pkg-fonts-devel