[MacPorts] #15052: pango: Font display problems when compiled against cairo 1.6.4

[MacPorts]

#15052: pango: Font display problems when compiled against cairo 1.6.4
--------------------------------+-------------------------------------------
  Reporter:  mike at it-loops.com  |       Owner:  ryandesign at macports.org
      Type:  defect             |      Status:  new                    
  Priority:  Normal             |   Milestone:  Port Bugs              
 Component:  ports              |     Version:                         
Resolution:                     |    Keywords:                         
--------------------------------+-------------------------------------------
Comment (by ryandesign at macports.org):

 Replying to [comment:16 macports at flyn.org]:
 > I would like to see a cairo variant build the Quartz font backend
 without the freetype backend. Once the Quartz GTK2 stack is stable,
 freetype should be unnecessary (two font engines is quite redundant)
 unless one wants to use X11 applications for their network-centricity. I
 think using "quartz" (build quartz & avoid freetype) and "no_x11" (avoid
 X11) like the GTK2 port will avoid confusion.

 A variant called "quartz" will make people think they need to use that
 variant to get Quartz functionality, which isn't true; Quartz
 functionality is always enabled on Mac OS X, since cairo 1.6.x.

 In MacPorts we usually like to build ports with maximal functionality. In
 this case, that would be a cairo port that supports as many backends as
 possible. That's what I do now. I could probably add a variant to disable
 fontconfig support, if there's a strong desire for that. Such a request
 should be made in a separate ticket. Note that all software that uses
 cairo must be written to support all backends. You can't just compile
 cairo with Quartz support and expect all cairo-using applications to know
 how to use Quartz. Each app must be written for this. Not all apps are. So
 there will likely be some cairo-using apps that need fontconfig. Even if
 today you only need GTK2 with only Quartz support, tomorrow you may want
 to install an unrelated app which happens to require cairo with
 fontconfig. So why not install a cairo with all possible backends in the
 first place? Which is what we offer now. (Except for glitz support. Which
 is in a variant. I don't know anything about glitz.)

 > GTK2's Portfile even says "cairo must be installed with the quartz
 variant enabled."

 That must be from the cairo 1.4.x days, when quartz support was still
 experimental, disabled by default, and therefore in a variant. In cairo
 1.6.x, the Quartz backend was marked stable, and enabled by default,
 therefore I removed the variant and integrated it into the core port.

-- 
Ticket URL: <http://trac.macports.org/ticket/15052#comment:17>
MacPorts <http://www.macports.org/>
Ports system for Mac OS