From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 0/2] Mono new package
Date: Tue, 28 Oct 2014 14:41:29 +0100 [thread overview]
Message-ID: <544F9D09.1010408@lucaceresoli.net> (raw)
In-Reply-To: <CA+TH9VngG20VsJqPQUkRT14u+w8_DB+U8f7pZWf3e9+nF7SR9A@mail.gmail.com>
Dear Angelo,
thank you for the follow-up.
Angelo Compagnucci wrote:
> Dear Luca,
>
>> BTW, Angelo, Thomas, where did you get licensing info when
>> writing/committing the package?
>
> Mono is a complex piece of software composed by several components, so
> the licensing scheme is complex. I'll try to summarize here.
Yes, it's very complex. If I were the Mono developer I'd probably split
each part in a different package. But this is not a Buildroot issue of
course.
Back in topic, I don't use Mono, hence I don't know the meaning of
"mcs", "gmcs", "jay", "boehm" etc, which doesn't help.
>
> The file COPYING.LIB is quite explicative:
Oops, I looked in LICENSE. The fact that there are at least 3 different
explanations (website, LICENSE and COPYING.LIB) does not help me either.
>
> "The Mono runtime is licensed under the terms of the GNU
> Library General Public License, version 2.
This is coherent with the website, while LICENSE states LGPL, without
specifying a version. So LGPLv2 should be correct.
>
> The eglib directory is licensed under the terms of the MIT
> X11 license and is a drop-in replacement for Mono's use of
> glib 2.0 (which was LGPL).
>
> The Boehm licensing information is in the libgc directory
>
> The SGen Garbage Collector is under the terms of the MIT X11
> license
>
> The class libraries under mono/mcs are unless otherwise stated
> under the MIT X11 license.
So eglib, boehm and the garbage collector are part of the runtime,
correct?
>
> Open source Microsoft code is licensed under the original terms
> which is either MS-PL for older components, or dual licensed
> MS-PL/Apache2 licensed."
But we have no mention of MS-PL nor Apache2 in MONO_LICENSE.
Where is the Microsoft code used? In the runtime?
>
> * The C# compiler is dual-licensed under the MIT/X11 license and the
> GNU General Public License (GPL).
>
> Every file inside mcs/mcs folder has this preamble "Dual licensed
> under the terms of the MIT X11 or GNU GPL"
>
> * The tools are released under the terms of the GNU General Public
> License (GPL).
>
> Not every file has a license in it's preamble, but the most part show
> a GPL preamble.
Uh, where are these "tools" located?
In the tools/ subdir I can't find any evidence of a GPL license:
$ git grep -i -C3 licens -- tools/ | grep -i general
$
Maybe you refer to another subdir?
>
> * The class libraries are released under the terms of the MIT X11 license.
>
> Every file inside mcs/class show a MIT.X11 preamble
>
> It's complex but it shows some sense!
> For the practical point of view of using it, you should comply with
> the license of the software you ship so the mono runtime and mono
> class only (LGPL2, MIT)
That's correct if you ship a target, not if you ship an SDK (which is
basically the stuff that is produced by Buildroot in output/host/).
If you do, you have host-mono in the SDK and this pulls in GPL and other
licenses.
Is my understanding correct?
>
> Hope this clarify!
Yes, it is less fuzzy now, thanks.
But unfortunately, due to my poor knowledge of the Mono project, I can't
build myself a strong opinion on what the correct MONO_LICENSE value
should be. But maybe you can further improve the current value starting
from my questions above (or clarify that the current value is ok).
Regards,
--
Luca
next prev parent reply other threads:[~2014-10-28 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 20:22 [Buildroot] [PATCH v6 0/2] Mono new package Angelo Compagnucci
2014-10-22 20:22 ` [Buildroot] [PATCH v6 1/2] package/monolite: " Angelo Compagnucci
2014-10-22 20:22 ` [Buildroot] [PATCH v6 2/2] package/mono: " Angelo Compagnucci
2014-10-25 8:50 ` [Buildroot] [PATCH v6 0/2] Mono " Thomas Petazzoni
2014-10-27 22:16 ` Luca Ceresoli
2014-10-28 7:21 ` Angelo Compagnucci
2014-10-28 13:41 ` Luca Ceresoli [this message]
2014-10-30 8:35 ` Angelo Compagnucci
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=544F9D09.1010408@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox