Bugzilla – Bug 154974
m17n-lib requires newer libotf
Last modified: 2006-03-06 10:32:06 UTC
Currently we have m17n-lib 1.3.0.20060113 in STABLE. m17n-lib used to link against libotf, but I found that it doesn't do that anymore: from: /work/built/dists/all/x86_64/packs-x86_64/m17n-lib/m17n-lib-1.3.0.20060113/Logfile.m17n-lib.spec: checking for OTF_check_features in -lotf... no ← missing feature! checking otf.h usability... yes checking otf.h presence... yes checking for otf.h... yes [...] config.status: executing depfiles commands The m17n library is configured with these external libraries. X11 Xaw fribidi freetype xft2 fontconfig anthy ispell ← libotf missing here + make The problem is that we still have libotf 0.9.3 but m17n-lib-1.3.0.20060113 requires libotf 0.9.4. When building against libotf 0.9.4 it works again: checking for OTF_check_features in -lotf... yes checking otf.h usability... yes checking otf.h presence... yes checking for otf.h... yes [...] config.status: executing depfiles commands The m17n library is configured with these external libraries. X11 Xaw fribidi libotf freetype xft2 fontconfig anthy ispell + make
I think we should update to libotf 0.9.4 to fix this, otherwise we have a regression compared to SuSE 10.0. Nothing else but m17n-lib depends on libotf, therefore updating libotf is safe.
updated package submitted to STABLE.
I guess you need to explain what libotf provides to m17n and if libotf contains crypto code.
The library "libotf" provides the following facilites. o Read Open Type Layout Tables from OTF file. Currently these tables are supported; head, name, cmap, GDEF, GSUB, and GPOS. o Convert a Unicode character sequence to a glyph code sequence by using the above tables. The combination of libotf and the FreeType library (Ver.2) realizes CTL (complex text layout) by OpenType fonts.
libotf does not contain crypto code: http://legaldb.suse.de/ldig/ldig-crypto.cgi?dig=libotf running: licensedigger -g -n -xp '/suse/jw/bin/grep_ldig crypto' libotf getpac -n libotf using /work/SRC/all/libotf running "tar jxf '/work/SRC/all/libotf/libotf-0.9.3.tar.bz2' -C '/tmp/ldig/libotf~1141396821/libotf-0.9.3.tar.bz2'" (238 kb) found 37 files. |/suse/jw/bin/grep_ldig crypto SSL libotf-0.9.3.tar.bz2/libotf-0.9.3/COPYING:350 the Library except as expressly provided under this License. Any SSL libotf-0.9.3.tar.bz2/libotf-0.9.3/aclocal.m4:45 dnl Quote A][M_PROG_GCJ so that aclocal doesn't bring it in needlessly. -- libotf-0.9.3.tar.bz2/libotf-0.9.3/src/otf.h:317 OTF_GlyphClassLigature = 2, -- libotf-0.9.3.tar.bz2/libotf-0.9.3/src/otfdrive.c:923 || ligg->GlyphClass > OTF_GlyphClassLigature)); clean up.
Package submitted again to STABLE with longer changelog entry: ------------------------------------------------------------------- Fri Mar 03 14:33:02 CET 2006 - mfabian@suse.de - Bugzilla #154974: update to 0.9.4. We have updated m17n-lib to 1.3.0.20060113. This version can only use libotf >= 0.9.4. It won't link against libotf 0.9.3. In order not to loose the OpenType support in m17n-lib, we should update libotf as well. -------------------------------------------------------------------
Package has been accepted and checked in. Closing as FIXED.