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
Fix gem build -C
#3954
Fix gem build -C
#3954
Conversation
160d135
to
e2bc2b2
Compare
I have pushed update which should fix the failing |
Hi @voxik. I'm now re-reading this patch and I think this does not solve the problem as expected. The help for the
However, in this patch, the gemspec is resolved before switching directories, so if it exists in the current directory, it will be taken from there. I would expect the given #3983 has been proposed fixing this issue as I would have expected, but maybe you had other expectations for the |
Done: #3988 |
The directory specified by `-C` option must be reflected, while the already loaded spec file must be used, wherever it came from. Fixes rubygems#3953
Done |
The directory specified by
-C
option must be reflected, while the already loaded spec file must be used, wherever it came from. This also fixes confusing messages when .gemspec file was not found at all.Fixes #3953
I have not tried to run the test suite, so let me see what is going to fail ...