Skip to content

Comment on The New Ruby Ecosystem

Comments

I do my dev on an archlinux box and the standard Ruby version in the repo (1.9.1_p378-2, I think) was doing something screwy to Jekyll.

After reading this article, I checked out RVM and installed a couple different Ruby versions to play with. If you're doing anything with Ruby, I'd definitely suggest checking it out. Set up a 1.8.7-head install inside of RVM and fixed all my Jekyll woes. It also gave me a chance to play with Rubinius and the latest 1.9.3dev release.

I always enjoyed being able to use eselect to switch between Ruby versions on Gentoo and RVM is able to duplicate this functionality and then some.

To the best of my recollection, Jekyll itself plays nicely with 1.9.1. It's Liquid that was a problem for me. The Gemcutter.org version of Liquid (2.0) is not 1.9 safe. However, the version at Github (2.1) is.

http://github.com/tobi/liquid

Since the commit to fix Liquid for 1.9.1 was in April of 2009, I wonder why it's not the version on Gemcutter? (Or some version of that version, if there are other issues...)

Edit: Yup, just checked. Jekyll with Liquid 2.1 is fine on 1.9.1. (I'm on OSX here, but the 1.9.1 I checked is also patch level 378.)

All of that said, rvm is outstanding.

Ruby 1.9.1 had some pretty serious threading issues, if I remember. 1.9.2 fixed them.

Don't know if that'd affect Jekyll, but I know it affected Rails.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.