veewee is back to fast gem releases, it is enough to gem install veewee
now
do not forget - rvm gemset globalcache enable
@i3zhe check rvm issues or open new one if the problem was not mentioned there yet => https://github.com/wayneeseguin/rvm/issues/
in the latest updates for RVM it is enough to:
rvm get head
rvm pkg remove
rvm install ruby
@justinko binstubs require an additional action (adding to PATH
), it's not fully safe as someone can add bin/rake
to your project with malicious code. Also binstubs are less intelligent, it's just a brute force - when in project use binstubs, you would need to reedit your PATH
to not include ./bin/
in case you would like to run command that is in Gemfile but you do no want to run it in context of the project.
There is a tool that automates the process a bit more: https://github.com/lsegal/rvm-tester and it has support for .travis.yml
.
please update the tags with ruby
- I found the same problem while codding ruby, never could understand why private definitions would have to be on top of the class.
try https://github.com/rubygems/rubygems/issues?milestone=2&page=1&state=open&utf8=%E2%9C%93 - it's not all, it does not include the described feature, but should be good overview of the fixed problems
Why people should not try other tools? Is there anything wrong with Rubygems - can you open tickets for Rubygems for the things that you think that are preventing people from using Rubygems and it's Gemfile support?
For long time I was under impression that Bundler will be slowly merging into Rubygems and that both teams were in agreement on that. But right now when part of the work is already done I see you (@indirect) are against the idea of merging. I have to say that hurts me as basically community has now to duplicate efforts on both tools. Is there any reason why we should not continue on improving also Rubygems support for Gemfile's?