freetype should be updated to latest version, diff inline

[michaelm@…]

diff -u -r1.5 Portfile
--- Portfile    3 Mar 2003 07:12:26 -0000       1.5
+++ Portfile    6 Jun 2003 16:38:03 -0000
@@ -2,7 +2,7 @@
 
 PortSystem 1.0
 name           freetype
-version                2.1.1
+version                2.1.3
 categories     print
 maintainers    eric@opendarwin.org
 description    Free and portable render engine for TrueType fonts
@@ -16,6 +16,6 @@
 use_bzip2      yes
 master_sites   http://switch.dl.sourceforge.net/freetype/ \
                http://prdownloads.sourceforge.net/freetype/
-checksums      md5 31e28bb0ebf008e5ac63540c79b2b687
+checksums      md5 09775a4111e066f782866d8a57d8481b

[ranger@…]

Just an FYI, having freetype around at all could cause a lot of issues (I know it's already there, just wanted to bring this up)

Since X11 already contains a libfreetype, things get really hairy when you have different versions installed at the same time. The thing is, there's no way in the ports system to guarantee any user using dports has the same version, since XFree86 4.3.0 comes with freetype 2.1.3 (which has a new symbol, FT_New_Face) and XFree86 4.2.1 (including Apple's X11) comes with an older version (which is missing that symbol).

Depending on the order libraries are linked and loaded, it's possible to have code that depends on *both* freetypes, which gives you runtime errors. It's really ugly, and the only way I've found to reliably make sure things are always consistent is to ONLY build against X11's freetype always.

To do so you have to modify anything that uses freetype to do:

  CFLAGS="-I/usr/X11R6/include"
  LDFLAGS="-L/usr/X11R6/lib"

...to force them first (or equivalent, if it's not an autotools build). If you try to do it the other way around (putting $prefix first) many builds inject their own X11 header/lib options first, or at random depending on what's in the makefiles, and things get mix-n-matched. It's very ugly.

Food for thought, I don't really know a good answer other than not having a freetype port at all. :P

[michaelm@…]

latest freetype now 2.1.4, see bug 500

* This bug has been marked as a duplicate of 500 *