[m-dev.] [m-users.] Closed source Mercury projects on Windows

Julien Fischer jfischer at opturion.com
Tue Jun 5 10:17:41 AEST 2018

Hi Mark,

On Tue, 5 Jun 2018, Mark Brown wrote:

> On Mon, May 28, 2018 at 12:25 PM, Peter Wang <novalazy at gmail.com> wrote:
>> (Having said that, LGPL with linking exception would be acceptable to me
>> as long as we follow an existing example.)
> Would you be happy with a pastiche of existing examples? On the face
> of it, the ocaml license seems to grant permission to link to someone
> else's modified version of the library. But I don't see how a license
> can work that way. I believe the last two sentences of the classpath
> license, on the other hand, would achieve the desired effect
> (classpath is GPL, not LGPL, but that's not relevant to this point).
> Below is text from ocaml, with the following changes:
> - it's about the Mercury Core Libraries (is that what we call them?)

I don't think we've ever given them a collective name before.
"core libraries" is fine by me.

> - LGPLv2, not v2.1 ("Library" not "Lesser")
> - you can link with *this* version (i.e., the version of Mercury that
> includes this exception), not with any public distribution
> - you can include the exception in modified versions of the library,
> if you choose
> Are there any objections to making this change? Any other suggestions?
> Mark
> diff --git a/COPYING.LIB b/COPYING.LIB
> index eb685a5..9ef923d 100644
> @@ -1,3 +1,25 @@
> +In the following, "the Mercury Core Libraries" refers to all source

I would delete "the".

> +code in the library, runtime, trace, browser and mdbcomp directories
> +in this distribution.

and java/runtime.


More information about the developers mailing list