1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Commit graph

18 commits

Author SHA1 Message Date
David Rodríguez
5b0abba931 Sync bundler & rubygems 2021-05-11 11:29:41 +09:00
David Rodríguez
2ab6b7a751 Remove no longer needed globs 2021-03-08 13:47:35 +09:00
Jakob Krigovsky
1feffe12d4 Link to pre-filtered issue list 2020-06-05 07:32:42 +09:00
Jakob Krigovsky
f9872c50cc Update links from rubygems/bundler to rubygems/rubygems 2020-06-05 07:32:42 +09:00
Hiroshi SHIBATA
9c2752296d Glob the all man files provided by bundler upstream 2020-05-22 20:32:30 +09:00
Hiroshi SHIBATA
a7c1791cec Partly reverted bundler.gemspec for ruby core testing 2020-05-13 07:54:37 +09:00
Hiroshi SHIBATA
0e60b59d58 Update the bundler version with master branch 2020-05-13 07:54:37 +09:00
David Rodríguez
5a384e2c08 Fix some bundler specs (#2380)
* These seem to consistenly pass already

* Show actual command when running `make test-bundler`

Current the setup command that installs the necessary gems for testing
bundler was printed, but not the actual command that runs the tests.
That was a bit confusing.

* Borrow trick from setproctitle specs

* A title that long doesn't get set sometimes

No idea why, but the test doesn't need that the title is that long.

* Fix most gem helper spec ruby-core failures

* Fix the rest of the gem helper failures

* Fix version spec by improving the assertion

* Remove unnecessary `BUNDLE_RUBY` environment var

We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name
because bundler considers `BUNDLE_*` variables as settings.

* Rename `BUNDLE_GEM` to `GEM_COMMAND`

This is more descriptive I think, and also friendlier for bundler
because `BUNDLE_` env variables are interpreted by bundler as settings,
and this is not a bundler setting.

This fixes one bundler spec failure in config specs against ruby-core.

* Fix quality spec when run in core

Use the proper path helper.

* Fix dummy lib builder to never load default gems

If a dummy library is named as a default gem, when requiring the library
from its executable, the default gem would be loaded when running from
core, because in core all default gems share path with bundler, and thus
they are always in the $LOAD_PATH. We fix the issue by loading lib
relatively inside dummy lib executables.

* More exact assertions

Sometimes I have the problem that I do some "print debugging" inside
specs, and suddently the spec passes. This happens when the assertion is
too relaxed, and the things I print make it match, specially when they
are simple strings like "1.0" than can be easily be part of gem paths
that I print for debugging.

I fix this by making a more exact assertion.

* Detect the correct shebang when ENV["RUBY"] is set

* Relax assertion

So that the spec passes even if another paths containing "ext" are in
the load path. This works to fix a ruby-core issue, but it's a better
assertion in general. We just want to know that the extension path was
added.

* Use folder structure independent path helper

It should fix this spec for ruby-core.

* Fix the last failing spec on ruby-core

* Skip `bundle open <default_gem>` spec when no default gems
2019-08-20 09:46:31 +09:00
David Rodríguez
8f28ae65a8 [bundler/bundler] Remove misleading comment in Gemfile
Since we no longer use `git` to find out the list of files, the comment
is misleading.

https://github.com/bundler/bundler/commit/54d85d5349
2019-08-16 14:30:23 +09:00
David Rodríguez
452516f50f
[bundler/bundler] Remove development dependencies from gemspec
And refactor development setup.

https://github.com/bundler/bundler/commit/f288806d02
2019-08-03 09:30:00 +09:00
David Rodríguez
31541d7389
[bundler/bundler] Drop rubygems 2.5.0 and 2.5.1 support
https://github.com/bundler/bundler/commit/8ecd722b9f
2019-08-03 09:29:58 +09:00
David Rodríguez
f8c03b24ca
[bundler/bundler] Bump rubocop to 0.72.0
https://github.com/bundler/bundler/commit/babbc112c6
2019-08-03 09:29:57 +09:00
David Rodríguez
df011b0238
[bundler/bundler] Lock rubocop-performance to 1.4.0
https://github.com/bundler/bundler/commit/595dd6af6c
2019-08-03 09:29:56 +09:00
David Rodríguez
1a8d9a0d5d
[bundler/bundler] Bump rubocop to 0.71
https://github.com/bundler/bundler/commit/efa69583dd
2019-08-03 09:29:56 +09:00
Hiroshi SHIBATA
57ccea6232 Revert to change for filelist of bundler gemspec. 2019-06-09 12:44:23 +09:00
Hiroshi SHIBATA
8f37629519 Merge bundler master from upstream.
Pick from 8dd59e3ba97eb80a599f8149f31bf40773b69dc0
2019-06-09 12:44:10 +09:00
hsbt
68ddd4d300 Merge Bundler 2.1.0.pre.1 as developed version from upstream.
a53709556b

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67539 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-04-14 06:01:35 +00:00
hsbt
7c9771be02 Fixed gemspec location of bundler.
FileCollector of rbinstall.rb requires location of gemspec under
  the sub-direcotry with the same name as default gems.

  I forgot to fix it with r66867.

  [Bug #15582][ruby-core:91374]

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66984 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-02-01 13:41:56 +00:00
Renamed from lib/bundler.gemspec (Browse further)