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

Don't use system gems when using system ruby #49

Open
cwolferh opened this issue Feb 7, 2013 · 0 comments
Open

Don't use system gems when using system ruby #49

cwolferh opened this issue Feb 7, 2013 · 0 comments

Comments

@cwolferh
Copy link
Contributor

cwolferh commented Feb 7, 2013

bootstrap.sh right now is rather fragile in "system ruby" mode. The problems tend to lie in the versions of gems that may already exist on the system, for instance, the oft-mentioned puppet bug that complains if a the puppet group does not exist. There has also been an issue with newer facter gems. And, rubygem-thor on Fedora 17 causes an issue later on during bundle install.

I think the solution is just to ignore system ruby gems, rather than try to the multitude of bugs we may face across distros / gem versions. In particular, this worked well for me on Fedora 17 with the "problem gems" already installed on the system.
cwolferh/dev-tools@master...less_fragile_system_ruby2

If there isn't an objection, I'll submit a pull request after #48 gets merged (they both touch one of the same lines in bootstrap.sh, so avoiding a merge conflict).

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

1 participant