-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Using binstubs for all gems with the deprecated --binstubs #3251
Comments
It looks like the original card for this issue mentioned an |
Actually We need to fix both the documentation and the deprecation message. |
Resolves rubygems#3251 Update the deprecation warning to point the user to the `--all` option for bundle binstubs as the preferred way to install binstubs for all gems in a bundle. Update `bundle binstubs` man page to include the `--all` option 🎉 and remove the note pointing to the now deprecated method of installing all binstubs.
Resolves rubygems#3251 Update the deprecation warning to point the user to the `--all` option for bundle binstubs as the preferred way to install binstubs for all gems in a bundle. Update `bundle binstubs` man page to include the `--all` option 🎉 and remove the note pointing to the now deprecated method of installing all binstubs.
FYI, the docs on the bundle website still don't document the |
Right, these docs will be present in bundler 2.2 docs. |
Docs are live now: https://bundler.io/v2.2/man/bundle-binstubs.1.html. |
Thanks |
I am trying to figure out how to properly set up bundler in Github actions, and bumped into what seems to be a missing or at least confusing functionality.
bundle install --binstubs
is deprecatedbundle binstubs
does not have a way to stub all gemsAnd, in addition it points to the deprecated
--binstubs
flag, which I am guessing is a documentation issue.So - what is the proper way to binstub all gems?
To add some context: When using a vendor path for the bundle (for caching), then any installed gem that comes with a binary, is not found in the path. This is why I started looking at this binstubs feature (which I never used before).
I would much rather avoid creating these binstubs, and instead, just add the
vendor/bundle/.../bin
folder to the path, but I was unable to find the proper command to obtain this path - as it seems to differ from system to system.I was hoping there is some
bundler env get bin_path
or similar so I can do this in GitHub Actions:The text was updated successfully, but these errors were encountered: