You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there's no mechanism (that I can find) in chef-rvm for automatically writing to your default.gems, and the mechanism for global.gems appears flawed. default.gems appears to be getting generated as the rvm defaults (which can wind up installing the wrong versions of rake and bundler), and global.gems is getting generated additively, so it contains the rvm defaults plus anything we've called with rvm_global_gem. Again, my use case is that I want specific, slightly old versions of bundler and rake, while rvm defaults to installing the newest ones.
Also, the entries added to global.gems don't include version number strings or source locations.
I'm currently reworking this for my purposes with templates instead, will pull request once I've got it working well if you're amenable.
The text was updated successfully, but these errors were encountered:
Yeah, totally! Looking back, I think I overlooked the default.gems and focused first on the global.gems to get bundler and stuff installed across the board. Looking at the rvm_global_gem provider I never got around to implementing the :remove and :purge actions (https://github.com/fnichol/chef-rvm/blob/master/providers/global_gem.rb#L88-119). Let me know if you need any pointers or help!
Currently, there's no mechanism (that I can find) in chef-rvm for automatically writing to your default.gems, and the mechanism for global.gems appears flawed. default.gems appears to be getting generated as the rvm defaults (which can wind up installing the wrong versions of rake and bundler), and global.gems is getting generated additively, so it contains the rvm defaults plus anything we've called with rvm_global_gem. Again, my use case is that I want specific, slightly old versions of bundler and rake, while rvm defaults to installing the newest ones.
Also, the entries added to global.gems don't include version number strings or source locations.
I'm currently reworking this for my purposes with templates instead, will pull request once I've got it working well if you're amenable.
The text was updated successfully, but these errors were encountered: