From: Alessandro Baretta <a.baretta@barettadeit.com>
To: OCaml <caml-list@yquem.inria.fr>
Subject: License question: tricky issue
Date: Tue, 07 Feb 2006 08:56:26 +0100 [thread overview]
Message-ID: <43E852AA.1020805@barettadeit.com> (raw)
Would the authors/copyright holders consider a tarball containing an Ocaml
source tarball plus other source code and other source tarballs as a
distribution of their software or as a derived work? The question is tricky due
to the non-free public license adopted by Inria originally.
I ask this question because I would like to release a source distribution for
Ocaml containing all source tarballs and all patches needed to build a complete
AS/Xcaml toolchain. This includes one or more stable ocaml tarballs, an
ocaml-cvs directory (for testing purposes), a metaocaml tarball, and a quite a
few libraries (findlib, pcre-ocaml, ocamlnet, pxp, extlib, postgres and a bunch
more). If I understand the QPL correctly, should this project be considered a
derived work I would not be allowed to distribute it; whereas, if it is
considered a distribution, à la Debian, there should be no problem.
Notice that all modifications to other peoples code exist in my distribution in
the form of patch files, which are automatically applied before the build
process begins.
Alex
--
*********************************************************************
Ing. Alessandro Baretta
Studio Baretta
http://studio.baretta.com/
Consulenza Tecnologica e Ingegneria Industriale
Technological Consulting and Industrial Engineering
tel. +39 02 370 111 55
fax. +39 02 370 111 54
next reply other threads:[~2006-02-07 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 7:56 Alessandro Baretta [this message]
2006-02-07 12:06 ` [Caml-list] " Sven Luther
2006-02-07 17:38 ` Xavier Leroy
2006-02-07 19:18 ` Alessandro Baretta
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=43E852AA.1020805@barettadeit.com \
--to=a.baretta@barettadeit.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