From ba7d4ce0d9deef5f9698398860637bdd7a8ea47b Mon Sep 17 00:00:00 2001 From: Stu Small Date: Fri, 13 Dec 2024 08:52:56 -0700 Subject: [PATCH] Switch from license-file to license According to the cargo docs, the license field is used when you have a standard license that has an existing SPDX 2.3 license expression. The license-file field should be used when you are using a non-standard license type that needs more details. So why does this matter? Some automated tools will parse these fields and use them as an input to license compliance checks. When using the license-file field it will go a more complicated path, where an MIT license should just get a rubber stamp from compliance. This change has no impact on the actual licensing, it just reflects it better in a machine parsable way --- Cargo.toml | 2 +- LICENSE | 21 --------------------- 2 files changed, 1 insertion(+), 22 deletions(-) delete mode 100644 LICENSE diff --git a/Cargo.toml b/Cargo.toml index d94393f..2ca4e63 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -6,7 +6,7 @@ edition = "2021" description = "This crate provides access to a set of strongly typed apis to interact with consul (https://www.consul.io/)" readme = "README.md" repository = "https://github.com/Roblox/rs-consul" -license-file = "LICENSE" +license = "MIT" # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html [features] diff --git a/LICENSE b/LICENSE deleted file mode 100644 index e64c5ce..0000000 --- a/LICENSE +++ /dev/null @@ -1,21 +0,0 @@ -MIT License - -Copyright (c) 2021 Roblox - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE.