-
Notifications
You must be signed in to change notification settings - Fork 100
Instructions for using 1.4.0 dev or other newer builds? #111
Comments
Check out hashicorp/vagrant#1461 . I think that's what you're looking for. |
Yes, you can either install pre-release versions from rubygems.org (or any other ruby repository), or install directly from the git repository. I have put instructions here. |
@jmahowald please see @johntdyer and @tmatilai's comments for proposed solutions. |
Thanks. Those helped. Since I had to figure some other bits out, thought I'd share in case anyone (like in #102) wanted to try this out. To build the gem I did Using bundler I did
Since it's in pre release, I couldn't use gem server, but instead used Gem in a Box. I ran into an issue, that I fixed by reading this thread (geminabox/geminabox#128). After doing that, I was able to install it running:
One more step that I had to do, because of issues with the cacerts in the embedded ruby in the vagrant omnibus installation not liking the ssl cert chain used at https://api.berkshelf.com.
|
Ah, sorry. I totally forgot this uses Thor instead of Rake... There shouldn't be need for any gem server. Allowing pre-release dependencies (until Berkshelf 3.0 is released) and explicitely using rubygems.org (until hashicorp/vagrant#2406 is resolved) should be enough:
|
Excellent) |
Hi @tmatilai, where exactly am I suppose to run these commands? |
@moleculezz In the cloned git repository. Bad and good news:
In above commands it's possible to also use Vagrant's embedded
(Instructions as a gist) |
I'm introducing berkshelf and we needed the mercurial support that is available in the 3.0 beta releases of berkshelf. Given that vagrant has it's own plugin system, I haven't yet figured out how to use your "pre release" versions of this plugin. Is there a way outside of telling everyone to use bundler?
The text was updated successfully, but these errors were encountered: