mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: vnsndalce@memeware.net
To: linux-kernel@vger.kernel.org, gentoo-user@lists.gentoo.org,
	ubuntu-users@lists.ubuntu.com, debian-user@lists.debian.org
Cc: rms@gnu.org, freebsd-women@freebsd.org, freebsd-chat@freebsd.org,
	misc@openbsd.org, esr@thyrsus.com, moglen@columbia.edu
Subject: Software distribution licenses are not "irrevocable as a rule"
Date: Fri, 04 Jan 2019 06:56:59 +0000	[thread overview]
Message-ID: <b4aa73e42abeb0ad1cc8191846ed8c8b@memeware.net> (raw)

>> 1016160

> The difference between you and them is that you believe that the GPL 
> requires consideration between licensee and grantor to be revocable. 
> Everybody else in the SFConverancy and the LKML disagree, a software 
> distribution license is non-revocable.

Incorrect. The SFConverancy tries to construe the clause I cited earlier 
as a promise not to revoke, thus inducing, by their argument, a 
reasonable reliance on the part of the taker that the permission will 
not be revoked.

THAT is their argument.

That clause is not what they pro-port it to be, nor would it be 
effective if not contracted for. It is not reasonable to rely on a term 
that you paid no consideration to the grantor for.

> a software distribution license is non-revocable.

Absolutely wrong. There is no such rule.

What you are thinking of, and you hinted at previously by calling the 
license a commercial license, is ... indeed, commercial software 
licenses where the taker pays consideration to the grantor.

In those cases, where there is a clause regarding revocation of the 
license, where the taker has payed for that license, the courts construe 
the contract to be one where those terms are not revocable because they 
are supported by the consideration the taker payed to the grantor.

THAT is why commercial software licensing contracts "are irrevocable".

Go read the cases. The fact that the consumer actually payed for the 
license is the deciding factor. He payed, he keeps what he payed for.

You did not pay? You did not pay linux coder 729 who is still a 
copyright holder to his code? Well your "interest" is unsupported as 
regards to that piece of linux coder 729's property.

                 reply	other threads:[~2019-01-04  6:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=b4aa73e42abeb0ad1cc8191846ed8c8b@memeware.net \
    --to=vnsndalce@memeware.net \
    --cc=debian-user@lists.debian.org \
    --cc=esr@thyrsus.com \
    --cc=freebsd-chat@freebsd.org \
    --cc=freebsd-women@freebsd.org \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=misc@openbsd.org \
    --cc=moglen@columbia.edu \
    --cc=rms@gnu.org \
    --cc=ubuntu-users@lists.ubuntu.com \
    /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

all inboxes | Powered by JetHome®