Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

[RubygemsIntegration] Add support for new activate_bin_path binstubs #4341

Merged
merged 1 commit into from
Mar 7, 2016

Conversation

segiddins
Copy link
Member

This ought to fix the build!

\c @indirect

@segiddins
Copy link
Member Author

(caused by rubygems/rubygems#1527)

@segiddins
Copy link
Member Author

@indirect r?

@indirect
Copy link
Member

indirect commented Mar 7, 2016

@homu r+

@homu
Copy link
Contributor

homu commented Mar 7, 2016

📌 Commit fcaab35 has been approved by indirect

@homu
Copy link
Contributor

homu commented Mar 7, 2016

⚡ Test exempted - status

@homu homu merged commit fcaab35 into master Mar 7, 2016
homu added a commit that referenced this pull request Mar 7, 2016
[RubygemsIntegration] Add support for new activate_bin_path binstubs

This ought to fix the build!

\c @indirect
@segiddins segiddins deleted the seg-rg-master-support branch March 7, 2016 05:17

redefine_method(gem_class, :bin_path) do |name, *args|
exec_name = args.first
return ENV["BUNDLE_BIN_PATH"] if exec_name == "bundle"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the new Gem.activate_bin_path will be missing out the chance to hit this early return and breaks this feature on bundle-exec's man page:

make sure that it's still possible to shell out to bundle from inside a command invoked by bundle exec (using $BUNDLE_BIN_PATH)

Not sure what would be the best way to fix it :-/
/cc @segiddins @indirect

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like you were right :) We're about to make this change on this PR #4992. I ran across this while researching a write up of a fresh commit message. It's been a long and winding road to re-discover what you'd found in March.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chrismo I'm feeling a bit guilty now for not being able to help fixing the issue a few months back.. But it was the first time I was reporting an issue with Rubygems and Bundler. There was a tendency to think I was missing something in the code and not fully understand the details. But thanks so much for the work on #4992. Looking forward to the release!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries, there are a lot of moving parts (as I continue to learn) and it can be a tough decision to know what matters and what will just be fine. At least you recorded this comment which helps confirm what we're seeing. :)

@segiddins
Copy link
Member Author

@taoza please open a new issue with steps to reproduce the bug you're seeing

@taonic
Copy link

taonic commented Mar 18, 2016

@segiddins Working on it :)

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

Successfully merging this pull request may close these issues.

None yet

6 participants