unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Packages, release notes, etc
Date: Fri, 11 Sep 2015 04:12:25 +0200	[thread overview]
Message-ID: <8737yl901i.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: mailman.878.1441927224.19560.help-gnu-emacs@gnu.org

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>>> With respect to license, I think it is not even possible for an Emacs
>>>> package to have a license different than GPL version 3 or later.
>>> Not exactly: the license can be different from GPLv3+, but it should
>>> be compatible with GPLv3+, indeed.
>> But what's the purpose of the copyleft when I can release a derived work
>> basing on GPL code under a GPL-compatible license which has no copyleft
>> anymore, e.g., Apache License, Version 2.0?
>
> You can't take existing GPL code and distribute it with an MIT
> license, indeed.  But you can distribute the code *you* write with
> an MIT license.
>
> You have to use a license that's compatible with the GPL not because
> it's a mere derivative of GPL'd code, but because that code can only
> work by linking with GPL'd code.  IIUC this is a theory that hasn't been
> tested in court.

Notice that what has been tested in court, is that a _translation_ is a
derived work, and subject to the copyright of the original copyright
holder.

And this is something that I would love to see tested in court, if
somebody took a GPL library written in, say lisp, translated it into
say C, and tried to distribute it under a different licence.

-- 
__Pascal Bourguignon__                 http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk


  parent reply	other threads:[~2015-09-11  2:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <vto7ccx8r5.ln2@news.c0t0d0s0.de>
2015-09-10  9:22 ` Packages, release notes, etc Tassilo Horn
2015-09-10 17:36   ` Stefan Monnier
2015-09-10 20:09     ` Tassilo Horn
2015-09-10 23:20       ` Stefan Monnier
     [not found]       ` <mailman.878.1441927224.19560.help-gnu-emacs@gnu.org>
2015-09-11  2:12         ` Pascal J. Bourguignon [this message]
2015-09-11  9:25           ` Alan Schmitt
2015-09-11  5:26       ` tomas
     [not found]     ` <mailman.874.1441915758.19560.help-gnu-emacs@gnu.org>
2015-09-11  0:16       ` Joost Kremers
2015-09-11  2:15         ` Pascal J. Bourguignon
     [not found] ` <mailman.808.1441876951.19560.help-gnu-emacs@gnu.org>
     [not found]   ` <ni18ccxbua.ln2@news.c0t0d0s0.de>
2015-09-10 10:31     ` tomas
2015-09-10 11:00       ` Tassilo Horn
2015-09-10 11:38         ` tomas
2015-09-10 11:40 Alexis

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737yl901i.fsf@kuiper.lan.informatimago.com \
    --to=pjb@informatimago.com \
    --cc=help-gnu-emacs@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).