Comment # 17 on bug 1206620 from Petr Gajdos

(In reply to Stefan Br���ns from comment #16)
> ImageMagick has a significantly more heavy dependency chain than
> GraphicsMagick, and IIRC this will also reintroduce a build cycle.

Which build cycle, could you elaborate with your knowledge, please?

> As it is used in quite some places as build dependency all these packages
> then will be in blocked state until ImageMagick has been rebuilt.

Perhaps yes, but I am not sure keeping GraphicsMagick for that reason only
outweigh the issues described in comment 0. I do not see many packages
requiring GraphicsMagick currently. That is why I am _considering_
GraphicsMagick removal now.

At least gmic fake dependency was discovered now. But yes, I have to admit that
I cannot be sure on the beginning we can get rid of GraphicsMagick completely,
no matter how sensible it sounds.