Skip to content

Share extracted bundled gems with gems for bundler #2922

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

Merged
merged 1 commit into from
Feb 25, 2020

Conversation

nobu
Copy link
Member

@nobu nobu commented Feb 24, 2020

Extract bundled gems under ".bundle/gems" and get rid of duplication which cause constant redefinition warnings at test-all after extract-gems and test-bundler.

Extract bundled gems under ".bundle/gems" and get rid of
duplication which cause constant redefinition warnings at
`test-all` after `extract-gems` and `test-bundler`.
@nobu nobu merged commit 55bf0ef into ruby:master Feb 25, 2020
@nobu nobu deleted the extract-bundled-gems branch February 25, 2020 11:40
@voxik
Copy link
Contributor

voxik commented Feb 26, 2020

I don't understand what is the purpose of this PR, but it seems to me, that now, the gems are installed from the .gem packages instead from their unpacked versions (the tarball ships both). This results in wrong shebang in "rake" binary, because Gem::Installer does not properly override the binary in contrast to UnpackedInstaller.

@voxik
Copy link
Contributor

voxik commented Feb 26, 2020

Just FTR, shipping the .gem packages as well as their unpacked counterparts always felt strange to me.

voxik added a commit to voxik/ruby that referenced this pull request Feb 27, 2020
The missing `\` in PR ruby#2922 causes the default gems to be installed from
the .gem packages instead from the expanded sources.
@voxik voxik mentioned this pull request Feb 27, 2020
nobu pushed a commit that referenced this pull request Feb 28, 2020
The missing `\` in PR #2922 causes the default gems to be installed from
the .gem packages instead from the expanded sources.
nobu pushed a commit to nobu/ruby that referenced this pull request Apr 1, 2022
The expanded gem location changed from 'gem' to '.bundled/gems'
directory in commit:git|55bf0ef1aa7c936b564b883196de1ace4be4cc7e /
 ruby#2922, leaving behind binary extension installation. This should fix
the issues, so the gem binary extensions are buildable as part of Ruby
build process again.
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

Successfully merging this pull request may close these issues.

3 participants