Arvados

run-build-packages builds distro packages for Ruby gems with something this command:

fpm -s gem -t $FORMAT --prefix "$FPM_GEM_PREFIX" "$gem_name"-*.gem

FPM_GEM_PREFIX is defined as:

if type rvm-exec >/dev/null 2>&1; then
  FPM_GEM_PREFIX=$(rvm-exec system gem environment gemdir)
else
  FPM_GEM_PREFIX=$(gem environment gemdir)
fi

There are a couple of problems with this:

• All of our Ruby requires Ruby 2.1. If the system Ruby is a different version, the path generated here won't be useful.
• If we're using RVM, there may not be a system gem command installed to ask for the gemdir. We need to be able to generate the gemdir without introspecting so much.

TBD:

• Do we want to take this opportunity to stop building these packages at all? I don't believe we recommend installing these packages through any guide at this time, instead preferring to deploy through Bundler, so they don't seem to be necessary.
• If we do want to keep building these packages, do we want to make sure that our build Docker images have Ruby 2.1 installed on the system (e.g., through some kind of backport), and build the distro packages more like our Python packages?