| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
7303: Refactor ruby core integration r=hsbt a=deivid-rodriguez
### What was the end-user problem that led to this PR?
The problem was that sometimes we break specs when integrating bundler changes into core.
### What was your diagnosis of the problem?
My diagnosis was that sometimes we use paths dependent on the structure of this repo, but that break under ruby-core's structure.
### What is your fix for the problem, implemented in this PR?
My fix is only some refactoring so that usage of structure independent helpers is encouraged. After this set of changes, if you grep the repo for `ruby_core?`, the only result will be `spec/support/path.rb`. That means that all logic dealing with repo folder structure lives in a single place.
### Why did you choose this fix out of the possible options?
I chose this fix because it makes the integration in core cleaner.
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
`FileUtils.rm` supports a `Pathname` argument.
|
| |
| |
| |
| | |
They are implicit inside `gem_command!`.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Since I plan to reuse it for something else.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Otherwise I get conflicts when extracting the helper.
|
| | |
|
| |
| |
| |
| |
| |
| | |
I want to extract these to path helper methods, but the name `files`
conflict with some builder methods that are also available at the same
level.
|
| |
| |
| |
| | |
The `:bundler` gem is not needed in the regular repo either.
|
| |
| |
| |
| |
| | |
The logic for choosing `gem_bin` should work here too even if it's not
identical.
|
| |
| |
| |
| | |
For debuggability.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Use shared helper instead.
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
7306: Fixup #7297 r=hsbt a=hsbt
### What was the end-user problem that led to this PR?
`build_metadata_spec.rb` was inconsistency structure.
### What was your diagnosis of the problem?
I missed checking the file location of #7297
### What is your fix for the problem, implemented in this PR?
Move file under `spec/bundler`.
### Why did you choose this fix out of the possible options?
Co-authored-by: Hiroshi SHIBATA <hsbt@ruby-lang.org>
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
7301: Track changes from ruby core master r=hsbt a=hsbt
### What was the end-user problem that led to this PR?
I'm going to merge https://github.com/bundler/bundler/pull/7274. But the ruby-core source has some of the changes for bundler source.
### What was your diagnosis of the problem?
### What is your fix for the problem, implemented in this PR?
ruby core team fixed them:
* Removed circular require warning at `shared_helper.rb`
* Support test at GitHub Actions, It helps that bundler will migrate Actions from Azure Pipelines too.
* Fixed broken examples at ruby core repository
### Why did you choose this fix out of the possible options?
Co-authored-by: ohbarye <over.rye@gmail.com>
Co-authored-by: Hiroshi SHIBATA <hsbt@ruby-lang.org>
Co-authored-by: Yusuke Endoh <mame@ruby-lang.org>
|
| | |
|
| |
| |
| |
| | |
Because it causes circular require.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
7242: Restore remembered options in manpages r=deivid-rodriguez a=uasi
### What was the end-user problem that led to this PR?
The problem was that the remembered options of `bundle install` were not documented in manpages.
### What is your fix for the problem, implemented in this PR?
Restore the section on remembered options from https://github.com/bundler/bundler/commit/e120f40f72fe53f55e05db9204f98d28f1065e81 and add description for some options.
### Why did you choose this fix out of the possible options?
They should be fully documented.
Closes #7198.
Co-authored-by: Tomoki Aonuma <uasi@uasi.jp>
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
|
| | |
| | |
| | |
| | | |
And instead educate users on the preferred, non deprecated, way.
|