From: Michael Ekstrand <michael@elehack.net>
To: caml-list@inria.fr
Subject: Re: Caml Light license in 2010
Date: Tue, 13 Jul 2010 20:23:05 -0400 [thread overview]
Message-ID: <i1j01a$prl$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTikPjEzoVdo4lf8TD22_0tntIfuVVmNy_2Vd-DvT@mail.gmail.com>
On 07/13/2010 09:18 AM, Jeremy Bem wrote:
> I'd like to use the Caml Light codebase as a jumping-off point for a new
> (language-level) functional programming project.. Also, I like to use
> public hosting (Google Code) for my projects. The problem however is
> the QPL license which means I need to maintain patchfiles rather than
> actual sources. This is awkward for version control and such.
Depending on what version control system you use, it might not be too
bad. If you use e.g. Mercurial with either mq (which gives nasty
history) or the pbranch extension, development might not be too painful.
pbranch is an alternative way of building patches by using Mercurial
branches to maintain them, leading to much cleaner history than a
versioned repository of patches. It does allow a checkout of the
modified source, though, so depending on how you make the repository
available that could be a technical violation of the license (although
the original state and applied changes will be clearly evident in the
revision log). I seem to remember a discussion about whether or not a
VCS is sufficient distinction to meet the requirements of the QPL, but
do not remember its outcome.
- Michael
next prev parent reply other threads:[~2010-07-14 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 13:18 Jeremy Bem
2010-07-14 0:23 ` Michael Ekstrand [this message]
2010-07-14 13:08 ` [Caml-list] " Stéphane Glondu
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='i1j01a$prl$1@dough.gmane.org' \
--to=michael@elehack.net \
--cc=caml-list@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).