Fix bundled gems installation on a fresh clone#2951
Merged
Conversation
5351ff1 to
b27447c
Compare
Contributor
Author
|
I messed something up apparently. I can try fix it, but I'd like to know if this is something you would like to fix since the linked issue was closed as intended behaviour. /cc @eregon as the original reporter of the ruby-core ticket. |
Member
|
👍 from me |
7505f68 to
1189374
Compare
nobu
reviewed
Mar 12, 2020
c4db4eb to
6e72254
Compare
Contributor
Author
|
@nobu pushed a few changes to master that made it very easy to fix this. Now CI is green. |
eregon
reviewed
Mar 13, 2020
6e72254 to
5f53728
Compare
nobu
reviewed
Mar 13, 2020
nurse
pushed a commit
to nurse/ruby
that referenced
this pull request
Mar 13, 2020
* Fix gem pristine not accounting for user installed gems. Pull request
ruby#2914 by Luis Sagastume.
* Refactor keyword argument test for Ruby 2.7. Pull request ruby#2947 by
SHIBATA Hiroshi.
* Fix errors at frozen Gem::Version. Pull request ruby#2949 by Nobuyoshi
Nakada.
* Remove taint usage on Ruby 2.7+. Pull request ruby#2951 by Jeremy Evans.
* Check Manifest.txt is up to date. Pull request ruby#2953 by David Rodríguez.
* Clarify symlink conditionals in tests. Pull request ruby#2962 by David
Rodríguez.
* Update command line parsing to work under ps. Pull request ruby#2966 by
David Rodríguez.
* Properly test `Gem::Specifications.stub_for`. Pull request ruby#2970 by
David Rodríguez.
* Fix Gem::LOADED_SPECS_MUTEX handling for recursive locking. Pull request
ruby#2985 by MSP-Greg.
5f53728 to
292c35a
Compare
Contributor
Author
|
Thank you! |
eregon
added a commit
to ruby/ruby-dev-builder
that referenced
this pull request
Mar 14, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, if you run
configure,makeandmake installon a fresh ruby clone,make installtries to install bundled gems, but fails to install anything.See the
make installoutput, where it succeeds to install default gems with and without extensions, and then tries to install bundled gems but fails to install anything.If at some point you happen to run
make update-gemsandmake extract-gems, then the proper.gemfiles and extracted gem contents are placed at the right place so thatrbinstall.rbcan see then, andmake installstarts doing the right thing.To me, this is clearly unintended, because if it was intentional,
make installwouldn't even try to install bundled gems by default.With this changes,
make installdoes the right thing by default:This PR fixes ruby bug https://bugs.ruby-lang.org/issues/13724.