From: Shawn Pearce <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Wolfgang Denk <wd@denx.de>, Jon Smirl <jonsmirl@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: Licensing and the library version of git
Date: Fri, 28 Jul 2006 23:56:32 -0400 [thread overview]
Message-ID: <20060729035632.GC28128@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0607281041420.29667@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Fri, 28 Jul 2006, Shawn Pearce wrote:
>
> > [...] as the GPL is incompatible with the Sun JRE runtime lirbary.
>
> This is not true. You can legally write and run GPLed software on the JRE
> runtime library.
>
> BTW I found an Eclipse plugin which is GPLed:
>
> http://www.eclipseplugincentral.com/Web_Links-index-req-viewlink-cid-651.html
Thanks. I did a little research on it myself after reading your
email. I turned up the following two pages from the FSF:
http://www.gnu.org/licenses/gpl-faq.html#InterpreterIncompat
http://www.gnu.org/licenses/lgpl-java.html
Both suggest that I can license everything under the GPL but provide
exclusions to allow users to run the code against its dependencies
which aren't GPL'd:
- the end-user may 'link' the code against any Java runtime library
of their choice;
- the end-user may 'link' the code against any Eclipse platform
or derivative of their choice;
So given that I'm seriously considering changing the license to
GPLv2 for the next version.
--
Shawn.
next prev parent reply other threads:[~2006-07-29 3:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 21:36 Licensing and the library version of git Jon Smirl
2006-07-27 1:40 ` Shawn Pearce
2006-07-27 11:41 ` Petr Baudis
2006-07-27 12:02 ` Johannes Schindelin
2006-07-27 12:54 ` Jon Smirl
2006-07-27 13:11 ` Petr Baudis
2006-07-27 16:11 ` Jon Smirl
[not found] ` <Pine.LNX.4.64 .0607270936200.4168@g5.osdl.org>
2006-07-27 16:38 ` Johannes Schindelin
2006-07-27 16:41 ` Linus Torvalds
2006-07-27 16:46 ` Linus Torvalds
2006-07-27 16:58 ` Jakub Narebski
2006-07-27 17:47 ` Jon Smirl
2006-07-28 0:25 ` Anand Kumria
2006-07-27 16:51 ` Grzegorz Kulewski
2006-07-27 17:07 ` Linus Torvalds
2006-07-27 19:31 ` Daniel Barkalow
2006-07-27 20:41 ` Johannes Schindelin
2006-07-27 18:42 ` David Lang
2006-07-27 19:44 ` Linus Torvalds
2006-07-27 19:49 ` David Lang
2006-07-27 20:38 ` Johannes Schindelin
2006-07-28 0:24 ` Anand Kumria
2006-07-28 0:43 ` Jon Smirl
2006-07-28 9:01 ` Johannes Schindelin
2006-07-27 14:04 ` Johannes Schindelin
2006-07-27 17:20 ` Petr Baudis
2006-07-27 17:23 ` Petr Baudis
2006-07-27 17:44 ` Linus Torvalds
2006-07-27 19:56 ` Wolfgang Denk
2006-07-27 20:39 ` Johannes Schindelin
2006-07-27 20:51 ` Petr Baudis
2006-07-27 21:06 ` Johannes Schindelin
2006-07-27 21:10 ` Wolfgang Denk
2006-07-27 21:16 ` Johannes Schindelin
2006-07-27 21:15 ` Linus Torvalds
2006-07-27 21:19 ` Johannes Schindelin
2006-07-28 5:04 ` Shawn Pearce
2006-07-28 8:44 ` Johannes Schindelin
2006-07-29 3:56 ` Shawn Pearce [this message]
2006-07-29 4:31 ` Jon Smirl
2006-07-29 11:21 ` Johannes Schindelin
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=20060729035632.GC28128@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=wd@denx.de \
/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).