From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml license
Date: Tue, 3 Jul 2007 07:22:35 +1000 [thread overview]
Message-ID: <20070703072235.52ce3d76.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <004201c7bcec$09a6f970$ac01a8c0@johnyaya>
Grant Olson wrote:
> Thanks, but I'm asking if I still need to indicate that I'm using LGPL code
> and reproduce the copywrite, or the the generated .exe is considered a
> separate work. That is, does it link to any of the LGPL code? And the same
> question with the Q-licensed components.
Have you read this:
http://caml.inria.fr/pub/old_caml_site/ocaml/LICENSE.html
I think that spells it out pretty thoroughly.
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
I hack, therefore I am.
prev parent reply other threads:[~2007-07-02 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 1:27 Grant Olson
2007-07-02 2:06 ` [Caml-list] " Christopher L Conway
2007-07-02 18:26 ` Eric Cooper
2007-07-02 21:00 ` Grant Olson
2007-07-02 21:22 ` Erik de Castro Lopo [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=20070703072235.52ce3d76.mle+ocaml@mega-nerd.com \
--to=mle+ocaml@mega-nerd.com \
--cc=caml-list@inria.fr \
/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).