Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Wishlist: integrate with outside Ruby installations like Chef-DK #314

Open
L2G opened this issue Jan 10, 2015 · 2 comments
Open

Wishlist: integrate with outside Ruby installations like Chef-DK #314

L2G opened this issue Jan 10, 2015 · 2 comments

Comments

@L2G
Copy link

L2G commented Jan 10, 2015

"Embedded" Ruby environments like Vagrant and the Chef Development Kit have their own ideas for where things are supposed to be placed. Chef-DK in particular has its own preferred settings for PATH, GEM_ROOT, GEM_HOME, and GEM_PATH that at present don't play well with chruby's method of managing these variables.

Right now I work around this by creating some monster Bash aliases, chefdk and unchefdk, that switch between Chef-DK's and chruby's way of doing things. But it would be nice to be able to do it all through chruby (e.g. chruby chefdk).

@postmodern
Copy link
Owner

We could potentially add a separate file that appends Chef's Ruby to $RUBIES. I'm not sure how we could handle custom GEM_ROOT, GEM_HOME without fundamentally breaking chruby. Also, why do you need to use chruby with Chef's embedded ruby?

@L2G
Copy link
Author

L2G commented Jan 14, 2015

Because, for whatever reason, the makers of the vagrant-berkshelf gem insist they won't support its use outside of the Chef Development Kit. But I do not want to be tied to one version of Ruby (the MRI 2.1.4 interpreter that ships with Chef DK).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants