Date: Fri, 12 Jul 2019 23:59:30 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 239165] print/freetype2: update to 2.10.0 Message-ID: <bug-239165-6497-FcBBFWtnF4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239165-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-239165-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239165 lightside <lightside@gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lightside@gmx.com Attachment #205741| |maintainer-approval?(gnome@ Flags| |FreeBSD.org) --- Comment #1 from lightside <lightside@gmx.com> --- Created attachment 205741 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D205741&action= =3Dedit 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=3Dpcf:no-long-family-names=3D1 -->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. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239165-6497-FcBBFWtnF4>