[oe-commits] [openembedded-core] 07/08: openssl: correct license comment

git at git.openembedded.org git at git.openembedded.org
Tue Oct 16 09:58:21 UTC 2018


This is an automated email from the git hooks/post-receive script.

rpurdie pushed a commit to branch master-next
in repository openembedded-core.

commit 09e29f827fcba8de144752d24b25cda568bf9d8f
Author: Paul Eggleton <paul.eggleton at linux.intel.com>
AuthorDate: Tue Oct 16 16:22:03 2018 +1300

    openssl: correct license comment
    
    The comment here stated that openssl is dual-licensed, but that would
    mean that either of the two licenses could be used which is *not* the
    case [1]. However LICENSE = "openssl" *is* correct because in OE that
    maps to a generic license file which includes both licenses, which
    makes sense because there isn't really any such thing as OpenSSL that
    would be covered by the "OpenSSL license" and not the "SSLeay license".
    Correct the comment to avoid any confusion.
    
    [1] https://www.openssl.org/source/license.html
    
    Signed-off-by: Paul Eggleton <paul.eggleton at linux.intel.com>
    Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
 meta/recipes-connectivity/openssl/openssl_1.1.1.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1.bb b/meta/recipes-connectivity/openssl/openssl_1.1.1.bb
index 0351858..0d80aba 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1.bb
@@ -4,7 +4,8 @@ HOMEPAGE = "http://www.openssl.org/"
 BUGTRACKER = "http://www.openssl.org/news/vulnerabilities.html"
 SECTION = "libs/network"
 
-# "openssl | SSLeay" dual license
+# "openssl" here actually means both OpenSSL and SSLeay licenses apply
+# (see meta/files/common-licenses/OpenSSL to which "openssl" is SPDXLICENSEMAPped)
 LICENSE = "openssl"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=d57d511030c9d66ef5f5966bee5a7eff"
 

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.


More information about the Openembedded-commits mailing list