Explicitly specify license in Cargo.toml #23
Merged
Conversation
This file contains 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
In the [docs for the Cargo manifest format](https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields), the use of `license-file` is only recommended for non-standard licenses. For standard licenses such as MIT, it should be specified in the `license` field explicitly. This change makes it easier for tools to correctly identify the license. For example, right now the license is identified as `non-standard` on both [crates.io](https://crates.io/crates/bevy-settings) and the [Bevy Assets page](https://bevyengine.org/assets/#persistence).
|
Thanks for noticing this |
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.
In the docs for the Cargo manifest format, the use of
license-fileis only recommended for non-standard licenses. For standard licenses such as MIT, it should be specified in thelicensefield explicitly.This change makes it easier for tools to correctly identify the license. For example, right now the license is identified as
non-standardon both crates.io and the Bevy Assets page.