Case insensitive file name matching when packaging files #13885
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.
Fixes #13722.
Handles the readme and license files. The
Cargo.lock
file is trickier. There are a bunch of places in the code where the existence ofCargo.lock
(case sensitive) is checked, including when packaging.I think it should be OK to keep
Cargo.lock
out of this. While the readme and license files are typically created by the user, theCargo.lock
file is typically created by Cargo, hence casing should be consistent anyway.This PR also doesn't handle a
TARGET
dir. I can look into that if desired.#13722 (comment)