[Xastir-Dev] Re: [Xastir] XASTIR <=> RH 8.0

[Jack Twilley]

>>>>> "James" == James Jefferson <jjeffers at aprsworld.net> writes:

James> Is there any reason why we have to stay on the bleeding edge of
James> ImageMagick?  Could we fork their code (from a working,
James> supported version) then freeze it.  At least that way we are
James> not always trying to hit a moving target. API changes are not
James> our friend!

Including our own copy of ImageMagick would be unwise for many
reasons.  An action like that would essentially be taking ownership of
the code -- we would be responsible for any security issues in that
code as well as any other maintenance.  We would also be increasing
the size of our package in a huge way.  It is much simpler and easier
to continue to chase along the ImageMagick path.  Perhaps it would be
helpful if Curt were to contact the ImageMagick authors and request
some sort of notice or documentation of forthcoming API changes.

Jack.
-- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
URL: <http://xastir.org/pipermail/xastir-dev/attachments/20021025/d014974f/attachment.sig>