Update freetype sources (2.6.2) in third party.

third_party/freetype2/README.chromium

 Name: freetype2
-URL: git://git.sv.nongnu.org/freetype/freetype2.git
-Version: 2.4.8-1ubuntu2.1
+URL: http://download.savannah.gnu.org/releases/freetype/

[viettrungluu, 2015/12/15 21:58:10]

I'd say "https", but their https is busted. D'oh. :-(

[Sean Klein, 2015/12/15 22:32:25]

Acknowledged :(

+Version: 2.6.2
 Security Critical: no
 License: BSD
 License File: NOT_SHIPPED

[viettrungluu, 2015/12/15 21:58:10]

Probably you should update this (to point to the LICENSE.TXT file).

[Sean Klein, 2015/12/15 22:32:25]

Done.

 
 Description:
 
-This mirrors the version of Freetype2 that was distributed with Ubuntu Precise
-(Version 2.4.8, git hash 9d7f0957fbd10fdbabf9815e37857a910ad4f4ac, plus
-applicable debian/patches-freetype as seen in
-https://launchpad.net/ubuntu/lucid/+source/freetype ). On Ubuntu Precise
-this code should be the same as the result of
-
-apt-get source freetype && cd freetype-2.4.8/ && ./debian/rules patch
-
-The build files should approximate the output of
-
-make -Bn | rev | cut -d ' ' -f 1 | rev | grep "\.c$" | sort
-
-Currently the cache, validators, patent checker (no longer used), and bzip2
-are excluded.
-
-We link this library into DumpRenderTree so that we can run the layout tests
-on later versions of Ubuntu and still get the same font rendering so that
-we don't have to support two sets of pixel test baselines.
+This mirrors the Freetype2, version 2.6.2.
 
 Freetype depends on two header files to be supplied by the user to specify
 how to build the library, ftconfig.h and ftmodule.h (or equivalent filenames
 as defined by the FT_CONFIG_CONFIG_H and FT_CONFIG_MODULES_H #defines).
 
-The versions in include/ were generated as follows (on a Precise machine):
+The versions in include/ were generated as follows (on a Trusty machine):
 
   % cd ext
   % bash autogen.sh
   % ./configure
   % cp objs/ftmodule.h ../include
   % cp builds/unix/ftconfig.h ../include
   % git apply freetype2.patch
 
 (Basically we use the stock list of modules, and define the FT_EXPORT
 and FT_EXPORT_DEF macros to work properly when building a linux shared lib.)
 
 This code is not considered security critical since it is only to be linked
 into test binaries! This should never be linked into chrome or any production
 code.