The libast ebuild has a depend on freetype-1* Not really sure if it needs to be freetype-1* , as installing here using freetype-2.1.5 seems to run fine (only running Eterm).
not a fonts issue, reassigning. afaics libast doesn't need freetype at all (anymore?)
libast doesnt link against freetype-2.x, it links against freetype-1.x root@vapier 0 libast # strings /usr/lib/libast.so | grep \\.so libImlib2.so.1 libttf.so.2 libX11.so.6 libSM.so.6 libICE.so.6 libdl.so.2 libm.so.6 libc.so.6 libast.so.1 does that mean freetype-1.x is even needed ? looking through the source, it never includes any freetype headers, and the only reference is a call to AC_CHECK_LIB() in the autoconf code ... i'll check upstream and get back to you
That is a very bad way to check actual deps and you should not use it to find them out. The freetype 1 linking is probably coming from Imlib2 and so shouldnt be included by libast itself.
Here I see: bob@kruus bob $ strings /usr/lib/libast.so |grep \\.so libImlib2.so.1 libX11.so.6 libSM.so.6 libICE.so.6 libpcre.so.0 libdl.so.2 libm.so.6 libc.so.6 libast.so.1 No link at all against freetype-1 (libttf.so.2) but a link to libpcre here.
Ah, libiml2 before the 1.1 release (1.0.6-r6) depends on freetype-1*, but the 1.1* depends on freetype-2*
foser: actually, it's not a bad way at all ... try to figure out the 'real' dependencies on a binary only package with `ldd` and you'll see how much extra cruft ldd will show and, if you look through the source like i did you'll find that the freetype-1.x is brought in by libast and is not actually needed i've talked to the author and it should be fixed upstream soon in the meantime, i've sed-out the linking from the configure script
