21700: Set GEM_PATH in Rails postinst

[arvados.git] / build / rails-package-scripts / postinst.sh

diff --git a/build/rails-package-scripts/postinst.sh b/build/rails-package-scripts/postinst.sh
index d0d5ef4408638701f8d086ea2eeb2278c8e2f96d..1d426baa730ba0eaa585159c3ba4f66091663cd0 100644 (file)
--- a/build/rails-package-scripts/postinst.sh
+++ b/build/rails-package-scripts/postinst.sh
@@ -200,6 +200,7 @@ configure_version() {
   # 3. We can know exactly where the `bundle` command got installed.
   local bundle_path="$SHARED_PATH/vendor_bundle"
   export GEM_HOME="$bundle_path/ruby/$(ruby -e 'puts RUBY_VERSION')"
+  export GEM_PATH="$GEM_HOME"
   run_and_report "Installing bundler" gem install --conservative --version '~> 2.4.0' bundler
   local bundle="$GEM_HOME/bin/bundle"
 
@@ -210,10 +211,11 @@ configure_version() {
   # which are already installed system-wide, which causes bundle activation to
   # fail later. Work around this by installing all gems manually.
   find vendor/cache -maxdepth 1 -name '*.gem' -print0 \
-      | run_and_report "Installing bundle gems" xargs -0r gem install --quiet
+      | run_and_report "Installing bundle gems" xargs -0r \
+                       gem install --conservative --ignore-dependencies --local --quiet
   # The earlier `bundle config` should have it looking for installed gems in
-  # the right place. Unset GEM_HOME now to be sure.
-  unset GEM_HOME
+  # the right place. Unset GEM_* now to be sure.
+  unset GEM_HOME GEM_PATH
   run_and_report "Running bundle install" "$bundle" install --prefer-local --quiet
   run_and_report "Verifying bundle is complete" "$bundle" exec true