From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libgdiplus: bump to version 5.6
Date: Tue, 1 May 2018 21:40:47 +0200 [thread overview]
Message-ID: <20180501214047.1d9f818c@windsurf.home> (raw)
In-Reply-To: <20180430190840.11455-1-fontaine.fabrice@gmail.com>
Hello,
+Sergio.
On Mon, 30 Apr 2018 21:08:40 +0200, Fabrice Fontaine wrote:
> # Although there is a LICENSE file thas specifies LGPL or MPL-1.1,
> # looks like it is incorrect. The actual source files specify that
> -# they're licensed under MIT, and so does the COPYING file (and they
> -# all predate the addition of the LICENSE file).
> +# they're licensed under MIT, and so does the original (before its
> +# removal/update) COPYING file (and they all predate the addition of
> +# the LICENSE file).
> LIBGDIPLUS_LICENSE = MIT
> -LIBGDIPLUS_LICENSE_FILES = COPYING src/carbon-private.h
> +LIBGDIPLUS_LICENSE_FILES = src/carbon-private.h
>
> LIBGDIPLUS_INSTALL_STAGING = YES
Hum, this feels weird. They have re-added a COPYING file pointing to
the LICENSE file, which itself that says LGPL or MPL, so perhaps this
isn't wrong after all ?
carbon-private.h might be MIT licensed, but the whole work may still be
released under LGPL or MPL.
See https://github.com/mono/libgdiplus/blob/master/LICENSE
So I believe our assessment that the LICENSE file was wrong when it was
saying LGPL or MPL-1.1 is not correct, and we should change the license
details of libgdiplus to LGPL-2.1 or MPL-1.1.
Sergio, you originally contributed libgdiplus, what do you think ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-01 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 19:08 [Buildroot] [PATCH 1/1] libgdiplus: bump to version 5.6 Fabrice Fontaine
2018-05-01 19:40 ` Thomas Petazzoni [this message]
2018-05-02 17:20 ` Sergio Prado
2018-05-02 21:37 ` Arnout Vandecappelle
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=20180501214047.1d9f818c@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.