From cedd23d4cc3eee43c9c2e5611e2bce13aa43ba55 Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Mon, 10 Nov 2014 07:52:56 -0500 Subject: [PATCH] Termination inevitability w/ aggregated GPLv2-only Most redistributors, at least with regard to embedded systems, typically include the kernel named Linux with their distribution. As such, even when GPLv2-or-later and/or GPLv3-{only, or-later} works are included in the aggregation, the termination implications are effectively those of GPLv2-only, since it's unlikely in any event the violator will remove the GPLv2-only work (particularly if it's Linux). --- compliance-guide.tex | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/compliance-guide.tex b/compliance-guide.tex index 4b8c1ee..1fbe50f 100644 --- a/compliance-guide.tex +++ b/compliance-guide.tex @@ -874,6 +874,16 @@ Given that much discussion of v3 has focused on its so-called more complicated requirements, it should be noted that v3 is, in this regard, more favorable to violators than v2. +However, note that most Linux-based systems typically include some software +licensed under GPLv2-only, and thus the copyright holders have withheld +permission to redistribute under terms of GPLv3. In larger aggregate +distributions which include GPLv2-only works (such as the kernel named +Linux), redistributors must operate as if termination is immediate and +permanent, since the technological remove of GPLv2-only works from the larger +distribution requires much more engineering work than the negotiation +required to seek restoration of rights for distribution under GPLv2-only +after permanent termination. + \chapter{Standard Requests} As we noted above, different copyright holders have different requirements