sexp_processor 4.0 gemspecs incompatibility about wrong

[goodsimon]

I resolved this with adding:

gem 'sexp_processor', '> 3.0'
gem 'wrong', '> 0.6.2'

to my Gemfile that was requiring 'wrong'. You won't get the latest sexp_processor but it will work.

[virgoproz]

I changed manually the gemspecs and all is good with the latest sexp_processor. Too bad this gem does not get updated.

Another issue is with RubyInline. I d love to use the 3.11+ but Wrong locks it to 3.9 (that contains deprecated code).

RubyInline-3.9.0/lib/inline.rb:375: Use RbConfig instead of obsolete and deprecated Config.

[alexch]

I'm in the process of upgrading Wrong to use Ryan's new versions of ruby_parser and ruby2ruby; hopefully that'll fix the sexp_processor and RubyInline fallout.

[virgoproz]

Awesomness!

On Sep 17, 2012, at 5:51 PM, Alex Chaffee [email protected] wrote:

I'm in the process of upgrading Wrong to use Ryan's new versions of ruby_parser and ruby2ruby; hopefully that'll fix the sexp_processor and RubyInline fallout.

—
Reply to this email directly or view it on GitHub.

[jneen]

With the latest release, @goodsimon's workaround breaks bundle install. Deleting the line makes it work again.

[goodsimon]

Good to know you're still looking out for us. We miss you @jayferd - talk to Joshua if you are looking for some "entertainment".

[alexch]

The latest Wrong has these deps:

s.add_dependency "predicated", "~> 0.2.6"
s.add_dependency "ruby_parser", ">= 3.0.1"
s.add_dependency "ruby2ruby", ">= 2.0.1"
s.add_dependency "sexp_processor", ">= 4.0"
s.add_dependency "diff-lcs", "~> 1.1.2"

After pushing Wrong 0.7.0, I had an odd situation where doing "bundle update wrong" in a different project somehow made bundler forget about predicated, but doing a plain "bundle update" worked fine.