On Saturday 29 November 2008 16.08.12 Okan Demirmen wrote: > One major issue/reason for keeping the current GraphicsMagick is > koffice3. I'm not sure we can simply drop the filter that is > dependent on the old GraphicsMagick - I've looked into it some, but > not enough; and koffice3 isn't going away anytime soon. What are the symptoms of koffice3 with newer GraphicsMagicks?
> Also note that GraphicsMagick 1.3.1 is out, the now current stable > release. Yeah, I thought about it first, but then I thought there is a reason why you didn't make your patch for 1.3 (my best guess was because of the OpenMP support). > I know of at least one existing port that would benefit from a new > GraphicsMagick, but I'm sure there are others. For what reason do > you need an update - new port or such? I needed the new version for gallery2 (which is not in ports, though). 1.2 has improved TIFF handling. > Talking out loud, if there are many ports that would seriously > benefit from switching to GraphicsMagick, from ImageMagick, I think every port can benefit from GraphicsMagick's stability and performance (over ImageMagick). > maybe we > could go down the route of splitting GraphicsMagick into 1.x/ and > stable/, or something. > > Oh, and I see that GraphicsMagick doesn't recommend gslib, so maybe > we should just disable that by default instead of making it a FLAVOR; I'm completely all right with that. Anyone using it, by the way? > then again, I wonder if we need a FLAVOR over a SUBPACKAGE - I > clearly haven't looked ;) > > There are a few things to consider, hence my lagging on this port. > Thanks for your interest though - opinions welcome ;) > > > [1] - > > http://leva.ecentrum.hu/patches/GraphicsMagick_1.2.6+no_gs.diff Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
