-
Notifications
You must be signed in to change notification settings - Fork 119
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
RubyGems install errors #7496
Comments
there's a lot of path manipulation being done in the recipes for |
Can take a look at it @jhheider. I imagine it's something to do with this comment. Do you know the reason this was needed? |
I don't offhand. It's likely |
Well @jhheider. I'm on darwin as well, and that's where the install error I posted above is happening. It can be replicated on darwin with:
However, it does only appear to be an issue with One other question. Why the discrepancy between these two ways of calling pkgx without install? |
Ah, yeah. The For invocation, |
If you happen to have an existing bundler at
/usr/local/bin/bundle
, then pkgx rubygems install fails with:This seems very wrong because
pkgx
doesn't even install anything to/usr/local
. So having an old bundle binary lying around shouldn't cause rubygems install to fail.But come to think of it, I've experienced a lot of weird things using
pkgx
rubies that cause subtle bundle install issues, and I suspect this faulty gem home might be the root of it. Inside a pkgx project when I rungem env
it has/usr/local
in my gem path:And it carries through to your
bundle env
as well:The value for
Gem Home
above should be whateverpkgx ruby -e 'puts Gem.user_dir'
evaluates to.Not sure what's happening, but I suspect pkgx
rubygems
needs to be more tightly coupled to pkgxruby
.The text was updated successfully, but these errors were encountered: