xfree-4.2.1 includes fontconfig, however it doesn't update the system to show that fontconfig is installed. This can cause problems with a new install or an install that already include fontconfig. This happened to me and I ended up unemerging all of xfree, qt, kde, and gnome to get the fonts working correctly again. (Antialiasing and missing fonts were included in the problems I had.) I think there may also be a problem when fontconfig is installed before xfree as it only requires freetype-2.0.9 while xfree-4.2.1 installs and uses freetype-2.1.2 which can cause linking problems when files are linked against one library and other dependent files are linked against the other lib. Suggestion would be to include a virtual/fontconfig which would be used by both the xfree-4.2.1 and by fontconfig. It would also be a good idea to make sure that they will be using the same libraries, as that might also later cause even more problems. Justin T
azarah@nosferatu patches $ /usr/sbin/epm -ql xfree | grep fontconfig azarah@nosferatu patches $ /usr/sbin/epm -qf /usr/lib/libfontconfig.so.1.0 fontconfig-2.0-r1 azarah@nosferatu patches $ --- The only thing that xfree uses from the fontconfig package, is Xft1.1. There was some problems with generating fonts.* and encodings.dir files, but they should be fixed in current version of 4.2.1 in portage. Anything that uses Xft, links to libXft, so is using the same freetype as xfree, else they link to the system freetype, which is of non consequence.
