Allow rebuilding erb outside a Git checkout - #131
Open
OskarEichler wants to merge 1 commit into
Open
Conversation
Member
|
What's the use case? This code is what almost everybody has in their gemspec and this is usually not a problem for them. Clearly, we don't need this for the rubygems.org releases. Do you have your own self-hosted ERB releases and get rid of Git after cloning the repository with Git? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Uses tracked files when Git is available and a filtered filesystem fallback otherwise, allowing the published source gem to be rebuilt without its missing .git directory.
Verified by building Git-checkout and Git-less archive gems with identical 21-file manifests and byte-identical outputs, plus the full compiled-native suite.