Resolve ActiveSupport version w/ old rubies

[afeld]

The gemspec does't set a max version for ActiveSupport, so the build is trying to install 4.x, which requires Ruby >= 1.9.3. Two possible solutions:

• Set a max version for ActiveSupport, e.g. s.add_dependency('activesupport', '>= 2.0.0', '< 4')
• Drop Ruby 1.8.7 and 1.9.2 support.

[jcn]

It probably makes sense to pin it to ActiveSupport < 4 at this point, unless there's anything explicitly in ActiveSupport 4 that would be helpful. As long as it's supported, we might as well maintain compatibility with older rubies.

[tolsen]

Does this mean that magickly would not be compatible with Rails 4 ?

Is there any way to require different versions based on the version of Ruby installed?

[afeld]

I was thinking of just starting a new major version w/ Rails 4+ support, but sounds like there is a way to do conditional gem support:

http://www.programmersparadox.com/2012/05/21/gemspec-loading-dependent-gems-based-on-the-users-system/

Will take a crack at it.

[afeld]

If that doesn't work, I'll just cut a new major version, and tell people they can use Magickly ~> 1.4 for Rails < 4 and Ruby < 1.9.3. Leaning this direction, actually, so that no extra effort needs to be put into supporting legacy platforms.

[afeld]

K, was just easier to drop support with a new major version than to try and support the old Rails/Ruby. We can make a 1-x-stable branch if we feel the need.