Include dependency license data in distributed packages #160
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.
resolves #155
This updates the packaging scripts to include dependency data in built distributable packages. Unfortunately the resulting script is somewhat fragile due to needing the environment just right for both the docker and non-docker build environments. I've attempted to comment the script for some of the pitfalls but it's hard to describe all the ways that things just wont work using the prebuilt ruby docker image. Sadly things work even less when using a custom docker image that installs ruby in a different manner.
In a short-ish description, the script works by
>= 2.0
version of bundler available atGEM_HOME
, noGemfile.lock
, and noBUNDLER_VERSION
env var setLICENSE
andREADME.md
as well as ruby'slicense.txt
All of the dependency data is put under a
meta
folder in the package, with a resulting structure like/cc @mlinksva for 👍 on the resulting structure and overall process.