caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: oliver <oliver@first.in-berlin.de>
To: "Török Edwin" <edwin+ml-ocaml@etorok.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Licenses - Confusion
Date: Fri, 24 May 2013 00:52:31 +0200	[thread overview]
Message-ID: <20130523225231.GA6510@siouxsie> (raw)
In-Reply-To: <519CC1C8.3060502@etorok.net>

Hi,

On Wed, May 22, 2013 at 04:02:00PM +0300, Török Edwin wrote:
> On 05/22/2013 03:34 PM, oliver wrote:
> > Hello,
> > 
> > I did publish one of my tools as GPLv3.
> > It is written in OCaml.
> > 
> > Now I saw at another project, that there is the need
> > for an "OCaml exception" regarding linking.
> > 
> > If thats true I may have missed a crucial points
> > when thinking about the license for tools written in OCaml.
> 
> I think that only matters if you release a *library* under LGPL.
[...]

OK, it seems, this is the point of distinction: if it is a library,
then the things, that were explained in this thread, about OCaml
and linking and checksums must be taken into account.

But when just publishing a program that should be used as is,
then it does not matter.

So, my questions were answered by you and others.

Thanks to all participants.


Ciao,
   Oliver


      parent reply	other threads:[~2013-05-23 22:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 12:34 oliver
2013-05-22 12:39 ` Anil Madhavapeddy
2013-05-22 16:40   ` Marek Kubica
2013-05-22 13:02 ` Török Edwin
2013-05-22 17:19   ` Adrien Nader
2013-05-23  6:36     ` Stéphane Glondu
2013-05-23  8:41       ` Daniel Bünzli
2013-05-23 21:07         ` Marek Kubica
2013-05-23 21:36         ` Stéphane Glondu
2013-05-23 22:28           ` Daniel Bünzli
2013-05-23 21:39         ` Ernesto Posse
2013-05-23 21:45         ` Chet Murthy
2013-05-23 22:11         ` Stefano Zacchiroli
2013-05-23 22:52   ` oliver [this message]

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=20130523225231.GA6510@siouxsie \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@inria.fr \
    --cc=edwin+ml-ocaml@etorok.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;
as well as URLs for NNTP newsgroup(s).