[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

freetype pre-release packages: testing needed

Hi folks,

I'm happy to report that there's been some positive progress regarding
freetype's pending ABI transition since I last posted about it[1].  In
response to concerns from a number of vendors about the disruptive effect
this transition would have on desktop distributions, freetype upstream has
done a tremendous job of restoring ABI compatibility with freetype 2.1.7 for
the upcoming 2.2 release.

Packages for freetype 2.2rc4 can be found at
<http://people.debian.org/~vorlon/freetype/>.  Please test them and let me
know what breaks!  In particular, it would be appreciated if users could
install freetype 2.2rc4 on sarge and confirm whether they're truly
compatible; these binary packages are built against etch, though, so you'll
need to rebuild to install it on sarge.

Testing the packages against testing/unstable is also appreciated.  So far,
the only suspected problem is with sdl-ttf in etch; everything else I've
tested works fine with this build of the package.  There seems to be a
rendering glitch of some kind, which I'm chasing up with upstream, but
in terms of binary compatibility it appears to check out and give us a
usable libfreetype6 for etch.

As part of this upgrade, freetype upstream is also decisively getting rid of
the internal header files that allowed the version skew to happen in the
first place.  This means that a number of packages that are poking at
internal freetype interfaces now will FTBFS once 2.2 reaches unstable.  See
http://www.freetype.org/freetype2/patches/rogue-patches.html for more
information on this.

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

[1] http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html

Attachment: signature.asc
Description: Digital signature

Reply to: