From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Yaron Minsky <yminsky@janestreet.com>
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>,
Jeremie Dimino <jdimino@janestreet.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] ocamlbuild on Windows and bash vs. cmd
Date: Tue, 11 Oct 2016 11:49:16 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CF8EECF@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <CACLX4jQxgD7Wz80LwV-sT46vut1EO6g_L4roAwGsAjvHcM09yQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]
Dear Yaron,
> I very much hope the licensing isn't an issue. We purposely picked a very liberal license to make this kind of thing as easy as possible. Do tell us if you find an issue there.
it is hard to believe, but the licensing is an issue. According to this reference from Apache:
https://www.apache.org/licenses/GPL-compatibility.html
citation:
“Despite our best efforts, the FSF has never considered the Apache License to be compatible with GPL version 2, citing the patent termination and indemnification provisions as restrictions not present in the older GPL license.”
the apache license you use is not compatible with GPL2. Since the OCaml library is LGPL 2.1, it cannot include Apache licensed code. The patent issue mentioned above has nothing to do with the difference between GPL and LGPL, so my guess would be that this also applies to LGPL 2.X.
Please note that the above reference states that Apache is compatible with GPL 3, but I guess you can write a PhD thesis in law and/or computer science about the topic if it is better to have GPL 2.x+ or GPL 3+Apache.
If you think it is worthwhile, I can ask one of our open source lawyers for advice, but I think the above statement from Apache is fairly clear.
So as it looks, I have to rewrite from scratch what I need - sigh
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
[-- Attachment #2: Type: text/html, Size: 7042 bytes --]
next prev parent reply other threads:[~2016-10-11 11:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 13:38 Soegtrop, Michael
2016-10-06 13:45 ` Kakadu
2016-10-06 14:01 ` Soegtrop, Michael
2016-10-06 13:55 ` Daniel Bünzli
2016-10-06 14:15 ` Soegtrop, Michael
2016-10-06 14:45 ` Gabriel Scherer
2016-10-06 16:16 ` Soegtrop, Michael
2016-10-06 17:45 ` Jeremie Dimino
2016-10-06 18:56 ` Gerd Stolpmann
2016-10-07 6:58 ` Soegtrop, Michael
2016-10-07 16:19 ` Yaron Minsky
2016-10-11 11:49 ` Soegtrop, Michael [this message]
2016-10-11 12:36 ` Yaron Minsky
2016-10-11 13:00 ` Ivan Gotovchits
2016-10-11 13:06 ` Anil Madhavapeddy
2016-10-11 13:13 ` Yaron Minsky
2016-10-11 13:27 ` Hendrik Boom
2016-10-11 13:53 ` Soegtrop, Michael
2016-10-11 15:48 ` Adrien Nader
2016-10-11 13:46 ` Soegtrop, Michael
2016-10-14 12:19 ` Manfred Lotz
2016-10-17 8:08 ` Soegtrop, Michael
2016-10-17 9:22 ` Manfred Lotz
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=0F7D3B1B3C4B894D824F5B822E3E5A172CF8EECF@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=jdimino@janestreet.com \
--cc=yminsky@janestreet.com \
/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;
as well as URLs for NNTP newsgroup(s).