caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
To: David Allsopp <dra-news@metastack.com>
Cc: Alexey Egorov <electreg@list.ru>, Adrien Nader <adrien@notk.org>,
	 "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml compiler license
Date: Fri, 6 Mar 2015 00:28:25 +0100	[thread overview]
Message-ID: <CAHvkLrMKK4xJL58mKGT_u+MSmfFFefyMXsuVyr0DvDRU2vryFw@mail.gmail.com> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9E9976B6B@Remus.metastack.local>

From the QPL 1.0 license in OCaml sources:

"... distribute your modifications, in a form that is separate from
the Software, such as patches."

In GIT, the software itself is a set of patches, so it's not so clear
for me that if the modifications are another set of patches, there are
in a "separate form".

Anyway, many people are distributing modified OCaml versions under
GIT, and INRIA has never complained about it, to the best of my
knowledge.

--Fabrice



On Fri, Mar 6, 2015 at 12:07 AM, David Allsopp <dra-news@metastack.com> wrote:
> Alexey Egorov wrote:
>> Hi Adrien,
>>
>> thanks for your reply.
>>
>> But wouldn't publicly avalable github repo with modified
>> sources violate license (just because non-patch/diff version
>> is publicly available)?
>
> IANAL, but if you put all your changes in a separate branch on your own git repo (forked from the official Git mirror) then you are literally storing a set of patches - the ability to download the entire distribution as one whole (or even as a .tar.gz file, say on GitHub) is just a convenience provided by the software, it's not what you're actually providing.
>
>
> David
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs



-- 
Fabrice LE FESSANT
Chercheur en Informatique
INRIA Paris Rocquencourt -- OCamlPro
Programming Languages and Distributed Systems

  reply	other threads:[~2015-03-05 23:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 17:38 Alexey Egorov
2015-03-05 19:41 ` Adrien Nader
2015-03-05 19:50   ` Alexey Egorov
2015-03-05 23:07     ` David Allsopp
2015-03-05 23:28       ` Fabrice Le Fessant [this message]
2015-03-05 23:54         ` Milan Stanojević
2015-03-06  7:41           ` Adrien Nader
2015-03-06  8:45         ` David Allsopp
2015-03-06  9:01           ` Roberto Di Cosmo
2015-03-06  9:08             ` David Allsopp
2015-03-06  9:31               ` Roberto Di Cosmo
2015-03-06  9:41                 ` David Allsopp

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=CAHvkLrMKK4xJL58mKGT_u+MSmfFFefyMXsuVyr0DvDRU2vryFw@mail.gmail.com \
    --to=fabrice.le_fessant@inria.fr \
    --cc=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=dra-news@metastack.com \
    --cc=electreg@list.ru \
    /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).