caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jonathan Roewen <jonathan.roewen@gmail.com>
To: caml-list@yquem.inria.fr
Subject: [Caml-list] Licensing questions
Date: Thu, 17 Nov 2005 14:03:59 +1300	[thread overview]
Message-ID: <ad8cfe7e0511161703h781d02e0p712ebff6a4e6d263@mail.gmail.com> (raw)

Hi,

I'm not a licensing guru, nor know exactly what all the gobbledegook
means, and have a few questions about how licensing of various parts
of ocaml system will affect my operating systems project.

I use a customised version of the sources in the following directories:
byterun
stdlib
otherlibs/threads
otherlibs/bigarray

Do I have to make those components open source? Also, can DST be
closed source if I so wish (currently haven't decided on a license)?

Kindest Regards,

Jonathan


             reply	other threads:[~2005-11-17  1:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  1:03 Jonathan Roewen [this message]
2005-11-17  8:00 ` David MENTRE

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=ad8cfe7e0511161703h781d02e0p712ebff6a4e6d263@mail.gmail.com \
    --to=jonathan.roewen@gmail.com \
    --cc=caml-list@yquem.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).