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

Re: Bug#316031: libfreetype6: API changes from 2.1.7 to 2.1.10

On Mon, Jun 27, 2005 at 10:29:55PM -0500, Ming Hua wrote:
> So from my understanding, it's urgent for libfreetype6 to bump its
> shlibs from "libfreetype6 (>= 2.1.5-1)" to "libfreetype6 (>= 2.1.10-1)".

No.  See bug #314385:  this library package's *name* needs to change,
because of the issue you describe below.

> A more serious problem, though, is that FreeType 2.1.10 dropped some old
> APIs.  I didn't follow freetype development, and the CHANGES
> documentation in freetype aren't very clear either.  Therefore I don't
> know if these APIs were private, or deprecated long ago, or anything
> else.  But them being dropped are causing many new problems.  The ones I
> am aware of right now are:  (1) mozilla-firefox FTBFS [2] on new
> libfreetype6-dev because it uses old FTC_Image_Cache_* API (superseded
> by FTC_ImageCache_*).  (2) gworkspace.app get undefined symbol
> FTC_Manager_Lookup_Size while using new libfreetype6 [3].

> So how should we deal with this issue?  I can't find a comprehensive
> list about what APIs are dropped from 2.1.7 to 2.1.10, and even if we
> have such a list, it's still hard to figure out which packages are using
> them.

It doesn't matter which ones are using them.  They were clearly exported as
part of the headers if packages are using them at all, which means that the
soname of the library *must* be changed, as well as the package name, and
packages depending on libfreetype6 must be recompiled.

Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature

Reply to: