seems i've missed a bit here while away...

2 things:

koffice 1.6 branch does not support newer GraphicsMagick versions.

i still don't understand the no_gs thing.  as kili pointed out, it can
be pinned down to removing the run dependency of ghostscript, but why?
for example, GraphicsMagick supports RAW images, hence a build
dependency on dcraw - should we force the user to read the output of gm
error messages to guess which additional package one needs to install to
get the compiled-in functionality?  i'm of the opinion 'no'.  same goes
with the gs binary being available if the package has been built to
support it.  is this a route any one wants to go down?

in any case, i think we should at least update to the latest 1.1.14
release.  i've kept the changes i made to make the port more like
ImageMagick; additionally, this builds the perl module and brings in
libwmf.

at least we don't break the current koffice3, for now.

http://www.demirmen.com/~okan/GraphicsMagick-1.1.14.diff

cheers,
okan

Reply via email to