From: "Yong Li" <yong.b.li@linux.intel.com>
To: "'Alexander Amelkin'" <a.amelkin@yadro.com>, <openbmc@lists.ozlabs.org>
Subject: RE: license conflicts with OpenSSL
Date: Mon, 2 Dec 2019 09:08:21 +0800 [thread overview]
Message-ID: <002701d5a8ac$fe40d280$fac27780$@linux.intel.com> (raw)
In-Reply-To: <b0b878b8-ff90-9e22-2831-44b086c0d8a2@yadro.com>
Thanks Alexander for your quick response!
My understanding is that you will perform some changes in the upstream
https://github.com/ipmitool/ipmitool, to remove these unused/obsolete
dependencies.
But I notice the ipmitool_1.8.18.bb file in openembedded is using these
.tar.bz2 files from sourceforge.net. Just want to know do you upload the new
versions to sourceforge.net?
Thanks,
Yong
From: Alexander Amelkin <a.amelkin@yadro.com>
Sent: Friday, November 29, 2019 7:28 PM
To: Yong Li <yong.b.li@linux.intel.com>; openbmc@lists.ozlabs.org
Subject: Re: license conflicts with OpenSSL
Hi Young and all!
I checked and I can say that ipmitool needs readline solely for ipmishell
support. I think that if ipmitool is confgured with --disable-ipmishell,
then there will be no license clash with readline as it won't be linked.
The requirement for ncurses looks totally obsolete. Nothing seems to change
if I just drop the requirement for tgetent(), which is what requires
ncurses. The tgetent() function is never called from anywhere in ipmitool
code. I think I will just drop the requirement for ncurses from ipmitool
soon.
With best regards,
Alexander Amelkin,
Maintainer of ipmitool
https://github.com/ipmitool/ipmitool
29.11.2019 9:56, Yong Li wrote:
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
next prev parent reply other threads:[~2019-12-02 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 6:56 license conflicts with OpenSSL Yong Li
2019-11-29 11:27 ` Alexander Amelkin
2019-12-02 1:08 ` Yong Li [this message]
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='002701d5a8ac$fe40d280$fac27780$@linux.intel.com' \
--to=yong.b.li@linux.intel.com \
--cc=a.amelkin@yadro.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.