From: "Grant Olson" <olsongt@verizon.net>
To: "'Christopher L Conway'" <cconway@cs.nyu.edu>
Cc: <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] Ocaml license
Date: Mon, 02 Jul 2007 17:00:34 -0400 [thread overview]
Message-ID: <004201c7bcec$09a6f970$ac01a8c0@johnyaya> (raw)
In-Reply-To: <4a051d930707011906t3ece47ccw9253d299932eff92@mail.gmail.com>
> -----Original Message-----
> From: christopherleeconway@gmail.com
>
> You shouldn't have to worry about the OCaml license at all.
> The LGPL allows you to distribute code that merely links
> against the standard library (as opposed to extending or
> modifying the library code) under a license of your choosing.
>
> Chris
>
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.
next prev parent reply other threads:[~2007-07-02 21:01 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 [this message]
2007-07-02 21:22 ` Erik de Castro Lopo
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='004201c7bcec$09a6f970$ac01a8c0@johnyaya' \
--to=olsongt@verizon.net \
--cc=caml-list@yquem.inria.fr \
--cc=cconway@cs.nyu.edu \
/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).