ports/68747: [patch] upgrade print/freetype2

[Koop Mast]

On Wed, 2004-07-07 at 12:14 -0400, Joe Marcus Clarke wrote:
> On Wed, 2004-07-07 at 11:10, Koop Mast wrote:
> > On Tue, 2004-07-06 at 22:02 -0400, Joe Marcus Clarke wrote: 
> > > On Tue, 2004-07-06 at 21:57, Mark Linimon wrote:
> > > > May I suggest that we hold off on this for a few days while we try to
> > > > work on the regression testing for the meta-X-upgrade stuff?  It's just
> > > > one more variable and there are plenty already :-)
> > > 
> > > Yeah, no problem.  I have to verify this myself.  Like I said, 2.1.8
> > > would have earned me much flamage.
> > > 
> > > Joe
> > 
> > Font look a little diffrent with 2.1.9 than with the freetype 2.1.7 but
> > I like them.
> > But the problem is that de freetype people have changed some api's,
> > somewhere in 2.1.8 and 2.1.9.
> 
> Do you have a screenshot example?  Specifically, what do the fonts in
> Evo look like?

http://rainbow-runner.nl/kwm/evo-freetype.png

The screenshot above is a 4.10-R machine running gnome 2.7, evolution
1.5.90.

> > 
> > Gnome and Xorg build fine with the new freetype but mozilla doesn't,
> > because it uses those changed api's. See: 
> > http://bugzilla.mozilla.org/show_bug.cgi?id=234035
> > 
> > With the patch in the bugreport mozilla build past the problem, but it
> > breaks later on. From a quick look its the same api changes.
> 
> Did you rebuild fontconfig and libXft as well as all the GNOME bits?  I
> guess this update is going to be fun.

Only fun if the port uses the changed api's (like mozilla).

I didn't rebuild fontconfig or the rest (on my 4.10-R box), but I
deleted the contence of /usr/X11R6 and /usr/local on my laptop (5.2-C
machine) and reinstalled everything against the new freetype.
So far, so good, well except for mozilla.

Koop

> 
> Joe
> 
> > 
> > Koop
> > 
> > > > 
> > > > mcl
> > 
> > _______________________________________________
> > freebsd-ports-bugs at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs
> > To unsubscribe, send any mail to "freebsd-ports-bugs-unsubscribe at freebsd.org"