maintainer-approval requested: [Bug 239165] print/freetype2: update to 2.10.0 : [Attachment 205741] Proposed patch (since 503401 revision)

[bugzilla-noreply at freebsd.org]

lightside <lightside at gmx.com> has asked freebsd-gnome mailing list
<gnome at FreeBSD.org> for maintainer-approval:
Bug 239165: print/freetype2: update to 2.10.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239165

Attachment 205741: Proposed patch (since 503401 revision)
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205741&action=edit



--- Comment #1 from lightside <lightside at gmx.com> ---
Created attachment 205741
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205741&action=edit
Proposed patch (since 503401 revision)

Hello.

I think, in case of LONG_PCF_NAMES option, possible to add some information
about pcf:no-long-family-names property to files/pkg-message.in file, based on
2.8 changelog:
https://sourceforge.net/projects/freetype/files/freetype2/2.8/
For example:
-8<--
If LONG_PCF_NAMES port's option was enabled, it can be disabled at run time
with
using pcf:no-long-family-names property. Example:

FREETYPE_PROPERTIES=pcf:no-long-family-names=1
-->8-

Also possible to include patches for closed bug reports after 2.10.1 release
(in files/patch-2.10.1.diff):
bug #56580: Type 1: Problem with (badly formed) SEAC glyph
https://savannah.nongnu.org/bugs/index.php?56580
bug #56601: Odd behavior with variable hinted font.
https://savannah.nongnu.org/bugs/index.php?56601
bug #56587: Direct-leak (OSS-Fuzz 12809)
https://savannah.nongnu.org/bugs/index.php?56587

Attached patch with proposed changes.