Move to graphicsmagick

Hello,
There was discution about problems of graphicsmagick today
on irc, it was 
started by Isaac, koffice debian packagers, the ABI
instability of 
ImageMagick is causing nightmare to release manager. And
it's API instability 
is causing problem to us. So I think we should make the move
to 
graphicsmagick which fix those issues. Has anyone a problem
with this ?
-- 
--- Cyrille Berger ---
_______________________________________________
kimageshop mailing list
kimageshopkde.org
http
s://mail.kde.org/mailman/listinfo/kimageshop

On Thursday 25 May 2006 12:37, Cyrille Berger wrote:
> Hello,
> There was discution about problems of graphicsmagick
today on irc, it was
> started by Isaac, koffice debian packagers, the ABI
instability of
> ImageMagick is causing nightmare to release manager.
And it's API
> instability is causing problem to us. So I think we
should make the move to
> graphicsmagick which fix those issues. Has anyone a
problem with this ?

The only reason I haven't done so was because I thought
graphicsmagick wasn't
packaged by distributions. If it is, or if we have enough
clout to get it
packaged, I think we should do it like greased lightning.

-- 
Boudewijn Rempt 
http://www.va
ldyas.org/fading/index.cgi
_______________________________________________
kimageshop mailing list
kimageshopkde.org
http
s://mail.kde.org/mailman/listinfo/kimageshop

> The only reason I haven't done so was because I
thought graphicsmagick
> wasn't packaged by distributions. If it is, or if we
have enough clout to
> get it packaged, I think we should do it like greased
lightning.
From irc:
12:02 < isaac> 12:00 < Riddell> developers
shouldn't not use something because 
it's not packaged, if a program needs it people will
package it unless 
there's some obvious problem with it

and I got flame for telling that there might be a problem,
anyway, we might, 
for the moment, keep the imagemagick and mark it as
deprecated, and have the 
graphicsmagick be activated over imagemagick if it is
available and have a 
configure message to warn the user that imagemagick is
deprecated and won't 
be maintained in the future.
-- 
--- Cyrille Berger ---
_______________________________________________
kimageshop mailing list
kimageshopkde.org
http
s://mail.kde.org/mailman/listinfo/kimageshop

On Thursday 25 May 2006 16:00, Cyrille Berger wrote:
> and I got flame for telling that there might be a
problem, anyway, we
> might, for the moment, keep the imagemagick and mark it
as deprecated, and
> have the graphicsmagick be activated over imagemagick
if it is available
> and have a configure message to warn the user that
imagemagick is
> deprecated and won't be maintained in the future.
Yeah that seems the best thing to do. It gives people the
ability to keep 
using it before it is in some distributions (like for people
wanting to use 
the dev version before the packagers package the
dependency).
Shouldn't be too much trouble to do either, especially in
the 1.6 branch, 
since we won't change much to the architecture there that
would require 
additional work to keep it working.

Bart
_______________________________________________
kimageshop mailing list
kimageshopkde.org
http
s://mail.kde.org/mailman/listinfo/kimageshop

On Thursday 25 May 2006 16:00, Cyrille Berger wrote:
> > The only reason I haven't done so was because I
thought graphicsmagick
> > wasn't packaged by distributions. If it is, or if
we have enough clout to
> > get it packaged, I think we should do it like
greased lightning.
> >From irc:
>
> 12:02 < isaac> 12:00 < Riddell> developers
shouldn't not use something
> because it's not packaged, if a program needs it
people will package it
> unless there's some obvious problem with it
>
> and I got flame for telling that there might be a
problem, anyway, we
> might, for the moment, keep the imagemagick and mark it
as deprecated, and
> have the graphicsmagick be activated over imagemagick
if it is available
> and have a configure message to warn the user that
imagemagick is
> deprecated and won't be maintained in the future.

Good. Feel free to take action  (But
don't forget the new cmyk saving bug, 
that's a biggie for 1.5.2)

-- 
Boudewijn Rempt 
http://www.va
ldyas.org/fading/index.cgi
_______________________________________________
kimageshop mailing list
kimageshopkde.org
http
s://mail.kde.org/mailman/listinfo/kimageshop

> Good. Feel free to take action  (But
don't forget the new cmyk saving
> bug, that's a biggie for 1.5.2)
I am working on it for tiff, as for png, as I said on the
bug report there is 
nothing I can do...
-- 
--- Cyrille Berger ---
_______________________________________________
kimageshop mailing list
kimageshopkde.org
http
s://mail.kde.org/mailman/listinfo/kimageshop

> So I think we should make the move to
> graphicsmagick which fix those issues. Has anyone a
problem with this ?
>
	As one of the maintainers of GM - I fully support this ;).


Leonard

_______________________________________________
kimageshop mailing list
kimageshopkde.org
http
s://mail.kde.org/mailman/listinfo/kimageshop