1
0
Fork 0
mirror of https://github.com/docker-library/ruby.git synced 2022-11-09 11:41:34 -05:00
Commit graph

6 commits

Author SHA1 Message Date
J0WI
27938afac2 Add Alpine 3.12 2020-06-11 00:38:42 +02:00
Nathan Ehresman
a564feaaee
Upgrade Ruby version 2.4.9 to 2.4.10, 2.5.7 to 2.5.8, 2.6.5 to 2.6.6, 2.7.0 to 2.7.1 (#310)
* Upgrade Ruby version 2.4.9 to 2.4.10, 2.5.7 to 2.5.8, 2.6.5 to 2.6.6, 2.7.0 to 2.7.1

* correct SHA256 hash values for the .tar.xz files

* updating Ruby version/hashes in a few missed files
2020-03-31 09:21:12 -07:00
David Rodríguez
82eecb7596
Alternative fix
Stop setting `BUNDLE_PATH`.

All default bundler versions shipped with all supported rubies install
gems to `GEM_HOME` by default, so this shouldn't be a breaking change
and it's a less surprising behavior because it does not deviate from how
bundler is configured by default.

Future versions will probably install locally by default, but that
hasn't happened yet.

I think leaving bundler "unconfigured" also matches the direction of the
recent change where the images no longer explicitly install `bundler` but
simply leave whatever version comes with ruby. Similarly, it makes sense
to me to leave whatever configuration comes by default with `bundler` in
place.
2020-01-03 18:05:39 +01:00
David Rodríguez
7df74adde3
Add paths scoped to ruby version to PATH and GEM_PATH
Newer bundler versions install gems to `$GEM_HOME/ruby/<ruby_version>`,
instead of directly to `$GEM_HOME`.

So we need to add the proper paths to `GEM_PATH` and `PATH` so that gems
and their executables are properly found.
2020-01-03 16:23:14 +01:00
David Rodríguez
8f3650c2ea
Remove unnecessary PATH modification
I don't think that folder exists :/
2020-01-03 14:31:14 +01:00
J0WI
defb10adcd Add Alpine 3.11 (#300) 2020-01-02 13:41:20 -08:00