4 commits

Author	SHA1	Message	Date
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
Jason Lee	e0f00b9a08	Upgrade to Ruby 2.7.0 GA (#301)	2019-12-27 09:27:26 -08:00