On Tue, 2006-10-31 at 23:34 +0100, Daniel Kobras wrote: > ImageMagick indirectly suggests to install the gsfonts package. (It > suggests to install gs which depends on gs-gpl which recommends gsfonts.) > That's probably too weak a link, and we should add an explicit > Recommends or Suggests on gsfonts to libmagick9.
That's fine if the goal is to have fonts in general. It doesn't really solve the underlying problem, though. We have fonts installed, just not the particular ghostscript ones that the ImageMagick package is expecting out of the box. Here's what's installed: ttf-bitstream-vera ttf-dejavu ttf-freefont After running the aforementioned script, we have a types.xml that properly matches our system. Perhaps this package should be using Defoma: "Defoma, which stands for DEbian FOnt MAnager, provides a framework for automatic font configuration. An application whose configuration of fonts usually requires manual intervention can automate the process through Defoma, by installing a Defoma-configuration script. The script gets called whenever a font is installed and removed, so that the script may update the application configuration." This could run a script to generate a proper types.xml file in /var/lib/ImageMagick (or similar), which ImageMagick would then use instead of what's now in /usr/lib/ImageMagick-6.2.4/config/ (using a symlink if necessary). Does this sound reasonable? > You can use environment variable MAGICK_CONFIGURE_PATH to add a > directory containing local tweaks to ImageMagick's search path without > modifying the packaged defaults. It's not very practical to have to set an environment variable and ensure it gets inherited all the way down to script running in Apache. Richard
signature.asc
Description: This is a digitally signed message part
