Skip to content

Conversation

@jamesprior
Copy link
Contributor

A small tweak for the ruby version - I'm using chruby and happen to have named my ruby 2.0.0 installation 'ruby200' instead of '2.0.0'. My goal here is to move the soft requirement of a matching ruby installation name into an explicit ruby version requirement in the Gemfile.

See http://bundler.io/v1.2/gemfile_ruby.html for the ruby declaration, bundle check will report

Your Ruby version is 1.9.3, but your Gemfile specified 2.0.0 

if the current ruby version does not match.

@jamesprior
Copy link
Contributor Author

So it appears I set up this pull request to point to the branch and not the commit, which means it has also updated to include the next pull I was going to suggest. I'm not 100% sure what other library we were using that defined $ but it was causing conflicts with the BCMS library. I've updated some of the BCMS JS to overtly use jQuery instead of relying on $ always being jQuery.

peakpg added a commit that referenced this pull request Jan 30, 2014
* Specify ruby version in Gemfile instead of a named rvm installation. * Wrap JQuery ready functions to avoid conflicts.
@peakpg peakpg merged commit 3fadcb9 into browsermedia:master Jan 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants