From: Peng Zang <peng.zang@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] License question - QPL vs. SCM
Date: Mon, 7 Apr 2008 15:10:16 -0400 [thread overview]
Message-ID: <200804071510.19669.peng.zang@gmail.com> (raw)
In-Reply-To: <47F9A346.4060900@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have no legal experience, I am not a lawyer etc ...
But this sounds okay. You're never actually distributing the changed form.
You are simply distributing the patches and software to automate the patching
process.
My opinion is probably biased though. I've always thought QPL was a silly
license. The whole idea that you can release source + patches but not the
patched sources seems absurd to me. There is no difference between the two.
All the necessary bits are there. It's like saying you can release the
source code in ASCII format but not UTF-8.
Peng
On Monday 07 April 2008 12:29:58 am Edgar Friendly wrote:
> The core OCaml compiler has a QPL license[1] (for everyone but
> consortium members). This license allows distribution as follows:
>
>
> 2. You may copy and distribute the Software in unmodified form
> provided that the entire package, including - but not restricted to -
> copyright, trademark notices and disclaimers, as released by the
> initial developer of the Software, is distributed.
>
> 3. You may make modifications to the Software and distribute your
> modifications, in a form that is separate from the Software, such as
> patches. ...
>
>
> My question for INRIA's lawyers (or anyone else in some official
> capacity to answer) involves using a Source Code Manager (SCM) whose
> distribution method has structure: source + patch1 + patch2 + .... The
> SCM would do the lifting of combining the two into the final tree, just
> as a script could easily wget an original source file and a list of
> patches and combine them into the final tree.
>
> Would using such a SCM to organize and distribute compiler source
> violate OCaml's license?
>
> Would using such a SCM make the Gods of OCaml angry? :) I don't intend
> to slip through a legal crack, I just want to work efficiently, and
> trying to manage patches without such a system seems like madness, like
> Linux kernel development before BitKeeper (I imagine).
>
> Edgar
>
>
> [1] http://caml.inria.fr/ocaml/license.en.html
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFH+nGbfIRcEFL/JewRAuIxAJ9iL1L19ea7MTVQlAsEHfINHCxW1wCfZ4hN
xkRVCHjL6l7KK1s3+gp8paw=
=Dgc7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-04-07 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 4:29 Edgar Friendly
2008-04-07 19:10 ` Peng Zang [this message]
2008-04-07 19:17 ` [Caml-list] " Adrien
2008-04-07 19:54 ` Dario Teixeira
2008-04-07 20:00 ` Sylvain Le Gall
2008-04-07 20:09 ` [Caml-list] " Edgar Friendly
2008-04-07 20:14 ` [Caml-list] " Peng Zang
2008-04-09 15:21 ` Xavier Leroy
2008-04-09 16:24 ` Edgar Friendly
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=200804071510.19669.peng.zang@gmail.com \
--to=peng.zang@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