From: "Yong Li" <yong.b.li@linux.intel.com>
To: <openbmc@lists.ozlabs.org>
Subject: license conflicts with OpenSSL
Date: Fri, 29 Nov 2019 14:56:46 +0800 [thread overview]
Message-ID: <000001d5a682$2b3fabd0$81bf0370$@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Hi All,
Just found that some packages included in openbmc have license conflict
issues between OpenSSL and GPL
Ipmitool package and krb5 package are both linked to openssl and other GPL
libs.
Based on the discussion in
https://lists.debian.org/debian-legal/2004/05/msg00595.html, I think they
are conflict licenses.
Just want to know if we need to do something? Such as add an additional
license file?
More information:
meta-openembedded/meta-oe/recipes-kernel/ipmitool/ipmitool_1.8.18.bb
LICENSE = "BSD-3-Clause"
DEPENDS = "openssl readline ncurses"
Readline is GPLv3
meta-openembedded/meta-oe/recipes-connectivity/krb5/krb5_1.17.bb:
LICENSE = "MIT"
DEPENDS = "bison-native ncurses util-linux e2fsprogs e2fsprogs-native
openssl"
Util-linux is GPLv2
Thanks,
Yong
[-- Attachment #2: Type: text/html, Size: 3881 bytes --]
next reply other threads:[~2019-11-29 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 6:56 Yong Li [this message]
2019-11-29 11:27 ` license conflicts with OpenSSL Alexander Amelkin
2019-12-02 1:08 ` Yong Li
2019-12-02 15:12 ` Alexander Amelkin
2019-12-04 2:18 ` Yong Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001d5a682$2b3fabd0$81bf0370$@linux.intel.com' \
--to=yong.b.li@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.