# RMagick prerequisite changes

**URL:** <https://www.ruby-forum.com/t/rmagick-prerequisite-changes/83433>\
**Category:** Ruby\
**Created:** [January 26, 2007, 12:46am UTC](https://www.ruby-forum.com/t/rmagick-prerequisite-changes/83433 "2007-01-26T00:46:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tim-hunter](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/278dde/32.png) [@tim-hunter](https://www.ruby-forum.com/u/tim-hunter)\
**Post date:** [January 26, 2007, 12:46am UTC](https://www.ruby-forum.com/t/rmagick-prerequisite-changes/83433/1 "2007-01-26T00:46:37Z")

</div>

Just a heads-up about the next major RMagick release:

The current release of RMagick, 1.15.0, supports ImageMagick \>= 6.0.0,  
Ruby \>= 1.6 (RVG requires Ruby 1.8), and all releases of GraphicsMagick.  
Testing RMagick with so many possible configurations has become  
impractical. Therefore the next major release of RMagick will be 2.0.0.  
RMagick 2 will require Ruby 1.8 and a recent version of ImageMagick,  
probably 6.3.0 or later. (The current version is 6.3.2.)

Regrettably RMagick 2 will not include support for GraphicsMagick.  
GraphicsMagick-only methods and constants (of which there are _very_  
few) will not be available. This breaks backward compatibility therefore  
I’m bumping the major version number. I believe the impact will be  
minimal and that 99.99% of all RMagick scripts will continue to run  
unchanged. I’d very much like to continue supporting GraphicsMagick  
(especially since GraphicsMagick’s maintainer, Bob Friesenhahn, has been  
a friend to RMagick since 2002) but its development has slowed and the  
two APIs have drifted apart considerably.

I don’t have a schedule for RMagick 2.0.0 but I’m guessing that it will  
be two or three months from now.

I’ll keep RMagick 1.15.0 available for as long as necessary and fix bugs  
for a reasonable period of time.

I hope that by updating RMagick’s prerequisites I can streamline the  
installation process and put RMagick in a better position for Ruby 1.9.  
Please let me know if you have any questions or concerns about this  
change.
