Use manifest file to specify set of files to include in gem #725
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.
Summary
Stop dynamically collecting files to include in the gem and instead specify (most of) them in a manifest file
Details
Use rake-manifest gem to generate and check a
Manifest.txt
file, and read that file in the gemspec to set the list of files to include in the gem. Also, run manifest checking task before gem building task.Motivation and Context
git ls-files
in gemspec #721)git ls-files
in gemspec #721 does not accurately exclude filesgit ls-files
in gemspec #721 needs parts of rake that may not be installed when e.g. Bundler is run to install dependencies, so just runningbundle install
to fetch dependencies from a fresh checkout doesn't work, leading to build failures on TravisCIHow Has This Been Tested?
Types of changes