[Bug 211201] print/freetype2: update to 2.6.5, replace LCD_FILTERING with V40 code

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211201

lightside <lightside at gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #172887|0                           |1
        is obsolete|                            |
 Attachment #172887|maintainer-approval?(gnome@ |
              Flags|FreeBSD.org)                |
 Attachment #172889|                            |maintainer-approval?(gnome@
              Flags|                            |FreeBSD.org)

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

(In reply to comment #16)
> The file documents how to use (included) licenses but isn't an actual license.
I included docs/LICENSE.TXT (as FREETYPE2) for informative purposes. It can be
removed for purist's purposes. Possible to create DOCS option with
PORTDOCS=reference CHANGES formats.txt LICENSE.TXT raster.txt

(In reply to comment #16)
> BOTH option may confuse users but can be eliminated via OPTIONS_GROUP at the
> cost of losing option helpers for the conditional.
The usage of OPTIONS_RADIO is correct (List of radio-choice grouped options: 0
or 1 among N).
Do you think V38 and V40 are more easy to understand? In overall options this
is correct and understandable: someone knows Infinality code, someone knows new
mininal code (a.k.a. ClearType), someone associates them with concrete versions
of TrueType interpreters (v35, v38, v40) as in source code.
Moreover, "Compile both" is used in ftoption.h:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/include/freetype/config/ftoption.h?id=VER-2-6-5#n619

(In reply to comment #16)
> # Note that though plus is allowed in a variable (and this license) name it
> # needs an extra space before following equals sign for them not to be parsed
> # as a single += operator
Yes, it works. Thanks.

The new proposed patch attached, related to license changes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.