The unfs3 license matches the SPDX template for BSD-3-Clause. There is no reason why this should be referenced as unfs3, which is not a registered SPDX identifier.
License-Update: use SPDX identifier Signed-off-by: Bastian Germann <[email protected]> --- meta/recipes-devtools/unfs3/unfs3_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/unfs3/unfs3_git.bb b/meta/recipes-devtools/unfs3/unfs3_git.bb index c5b7898b3c..0a274d6ffd 100644 --- a/meta/recipes-devtools/unfs3/unfs3_git.bb +++ b/meta/recipes-devtools/unfs3/unfs3_git.bb @@ -4,7 +4,7 @@ specification. It provides a daemon for the MOUNT and NFS protocols, which \ are used by NFS clients for accessing files on the server." HOMEPAGE = "https://github.com/unfs3/unfs3"; SECTION = "console/network" -LICENSE = "unfs3" +LICENSE = "BSD-3-Clause" LIC_FILES_CHKSUM = "file://LICENSE;md5=9475885294e17c0cc0067820d042792e" DEPENDS = "flex-native bison-native flex"
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#210501): https://lists.openembedded.org/g/openembedded-core/message/210501 Mute This Topic: https://lists.openembedded.org/mt/110925861/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
