Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Cannot edit default.gems, no versions in global.gems #63

Closed
bensomers opened this issue Jan 19, 2012 · 2 comments
Closed

Cannot edit default.gems, no versions in global.gems #63

bensomers opened this issue Jan 19, 2012 · 2 comments

Comments

@bensomers
Copy link

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.

@fnichol
Copy link
Contributor

fnichol commented Jan 21, 2012

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!

phlipper pushed a commit to newleaders/chef-rvm that referenced this issue Feb 1, 2012
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

3 participants