Replace existing install script with a newer one that uses gem-based installation #108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Natalie Perlin <Natalie.Perlin@noaa.gov>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The existing install script is problematic in that it requires maintenance of hand-built and hand acquired tarballs as well as compiling libraries. This exposes the installation to many potential points of failure and requires systems to have
ruby-develdevelopment OS packages installed. The existing installation strategy was originally required due to air-gapping of systems such that direct gem installation was not possible. However, this is no longer the case. This PR updates the installation of dependencies to use a direct gem install process.