On Mon, Nov 21, 2005 at 11:45:05AM +0100, Loic Minier wrote: > On Mon, Nov 21, 2005, Steve Langasek wrote: > > This procedure should be avoided except in cases where the library is > > important enough to keep around for binary compatibility with software > > external to Debian. I don't have reason to believe this is the case for > > libfreetype; do you?
> I'm not sure of what you mean, but I thought the rdeps of libfreetype > (mostly via gtk) made it important enough to warrant such care. I mean that the only reason to ship an old freetype in etch is for compatibility with other software that we don't control; so if that's not an issue, we should be transitioning Debian as quickly as possible to the new version, rather than carrying two versions around (which, btw, would probably cause segfaults). > Anyway, your preferred option seems saner, and quite doable given the > limited amount of API / ABI changes as listed by mdz. Other symbols removed since 2.1.7, btw: FTC_Manager_Register_Cache -> FTC_Manager_RegisterCache FT_LruList_Destroy -> FTC_MruList_Done? FT_LruList_Lookup -> FTC_MruList_Lookup? FT_LruList_New -> FTC_MruList_New? FT_LruList_Remove -> FTC_MruList_Remove? FT_LruList_Remove_Selection -> FTC_MruList_RemoveSelection? FT_LruList_Reset -> FTC_MruList_Reset? ftc_cache_clear -> FTC_Cache_Clear ftc_cache_done -> FTC_Cache_Done ftc_cache_init -> FTC_Cache_Init ftc_cache_lookup -> FTC_Cache_Lookup ftc_family_done -> ? ftc_family_init -> FTC_Family_Init ? ftc_family_table_alloc -> ? ftc_family_table_free -> ? ftc_glyph_family_done -> ? ftc_glyph_family_init -> ? ftc_glyph_node_compare -> ? ftc_glyph_node_done -> ? ftc_glyph_node_init -> ? ftc_node_done -> FTC_GNode_Done ? Symbols that are removed and are not mentioned in the headers for 2.1.7, but who knows whether that means they were part of the interface earlier :/ : BitOrderInvert -> ? FourByteSwap -> ? RepadBitmap -> ? TwoByteSwap -> ? Even worse, though, is the number of symbols *added* -- 75 new symbols, vs. 32 removed. Since the maintainer did not bump the shlibs when uploading, either, there's no way to determine which packages are using the new ABI except by looking at upload dates. I'm afraid that a library transition may be the only sane option after all... :/ -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
