Skip to content

Commit

Permalink
Updated gemsets to use final release of Bundler.
Browse files Browse the repository at this point in the history
  • Loading branch information
@jbhannah @wayneeseguin
jbhannah authored and wayneeseguin committed Aug 30, 2010
1 parent 454fa3c commit a64e619
Show file tree
Hide file tree
Showing 5 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion gemsets/jruby/global.gems
View file
@@ -1,2 +1,2 @@
jruby-openssl
bundler -v1.0.0.rc.5 --pre
bundler
2 changes: 1 addition & 1 deletion gemsets/rbx/global.gems
View file
@@ -1 +1 @@
bundler -v1.0.0.rc.5 --pre
bundler
2 changes: 1 addition & 1 deletion gemsets/ruby/1.8.7/global.gems
View file
@@ -1 +1 @@
bundler -v1.0.0.rc.5 --pre
bundler
1 change: 0 additions & 1 deletion gemsets/ruby/1.9.1/global.gems
View file

This file was deleted.

1 change: 1 addition & 0 deletions gemsets/ruby/1.9.1/global.gems
View file
@@ -0,0 +1 @@
bundler
1 change: 0 additions & 1 deletion gemsets/ruby/1.9.2/global.gems
View file

This file was deleted.

1 change: 1 addition & 0 deletions gemsets/ruby/1.9.2/global.gems
View file
@@ -0,0 +1 @@
bundler

5 comments on commit a64e619

@wayneeseguin
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, care to do a pull request?

@mag
Copy link

@mag mag commented on a64e619 Oct 22, 2010

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I'm writing scripts that can spin up servers on EC2 and install my rails application. I'd like this to happen in a deterministic manner; if I don't change my code, I'd expect the exact same set of software to end up on the box.

Unless I'm reading this wrong, RVM foils this by always installing the latest/greatest bundler gem in the global gemset for each interpreter. Depending on when you run - even if you run with the same version of RVM - this could leave your box in a different state than previous runs.

My solution to this is to blow away these global.gems files before I install any ruby interpreters, and then install the exact version of bundler I want. This works fine, but I feel like RVM's dependencies should behave this way by default. Can this be achieved? Easiest way that I can imagine is to add a hardcoded Bundler version to this file and its ilk. But obviously that's a bit painful as it requires human intervention to update the version of bundler that RVM points to.

Other ideas, or thoughts?

Thanks for listening!
Mike

@morgoth
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi mag.
I had similar problem - I'm installing rvm by chef-client and I also want to know which gems will be installed.
So my solution was to simply remove this global.gems file and install them on my own. Also if you need script for installing custom version of rvm, here it is:

mkdir -p ~/.rvm/src/ && cd ~/.rvm/src && rm -rf ./rvm/ && git init rvm && cd rvm && git pull git://github.com/wayneeseguin/rvm.git tags/1.0.11 && ./install

This will take code tagged i.e. as 1.0.11

@wayneeseguin
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mag,

Simply replace the .gems files with your specific default / global gem lists.

@mag
Copy link

@mag mag commented on a64e619 Oct 27, 2010

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's what I did, thanks Wayne.

Mike

Please sign in to comment.