[Pkg-fonts-devel] Bug#504705: python-fontforge: fontforge Revision 1.2945
Followup-For: Bug #504705
I think it's explained by this fontforge revision comment:
Revision 1.2945 - (download)
Sun Nov 2 03:20:50 2008 UTC (4 days, 12 hours ago) by pfaedit
Changes since 1.2944: +2 -2 lines
Distributions no longer provide .so files -- unless you ask for -dev
packages, and sometimes those don't exist. This means that dlopening a
library doesn't work. I think that's really stupid on the
distibutioner's part. What do they gain by removing the .so file? But
I won't even try to change their minds. Instead try to open the
appropriate foo.so.? file if we can't find foo.so (Not always, but in
the more important cases).
So either python-fontforge depends on libfontforge or somehow move .so
files to libfontforge1 or add the patch.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=zh_CN.GBK (charmap=GBK)
Shell: /bin/sh linked to /bin/bash
Versions of packages python-fontforge depends on:
ii libc6 2.7-16 GNU C Library: Shared libraries
ii libfontforge1 0.0.20080927-1 runtime library for FontForge
ii python 2.5.2-3 An interactive high-level object-o
ii python-support 0.8.7 automated rebuilding support for P
python-fontforge recommends no packages.
python-fontforge suggests no packages.
-- no debconf information