Re: [cups-devel] CUPS License Change Coming

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)

--Boundary_(ID_gyBSUzsJC2T8b0iuVjNZMQ)
Content-type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary=3xuXi8U4rWrVVqXbqJIP8p84O6ohkvTnW

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--3xuXi8U4rWrVVqXbqJIP8p84O6ohkvTnW
Content-Type: multipart/mixed; boundary="FLjJTWopP1hwfLPJTRsceAFnoowVD48Xh";
 protected-headers="v1"
From: Zdenek Dohnal <[email protected]>
To: [email protected]
Message-ID: <7eb0e58a-19aa-dd50-4c65-3592f6ae7982-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [cups-devel] CUPS License Change Coming
References: <2E55FEEC-11BA-4789-B6F8-C6CCC27A8884-2kanFRK1NckAvxtiuMwx3w@public.gmane.org>
 <50950267-3c73-5886-8ff4-ca245b7519c7-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
 <37cb406c-a063-7295-0c47-966f67a1f9d2-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
 <[email protected]>
In-Reply-To: <[email protected]>

--FLjJTWopP1hwfLPJTRsceAFnoowVD48Xh
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

On 12/01/2017 10:54 AM, Didier 'OdyX' Raboud wrote:
> The problem is still that such a license change for CUPS forces GPL2-on=
ly
> upstream authors (such as gutenprint) who used to link against CUPS to =

> relicence to a compatible license (GPL-2+ or GPL-2 with a CUPS-specific=
=20
> exception). And that's far from easy: it's de facto only possible iff a=
ll=20
> present and past copyright holder unanimously agree, or have waived the=
ir=20
> rights to an organisation registered as sole copyright holder (or such)=
=2E
>
> tl:dr; For Debian, CUPS' license change will imply that no GPL-2-only s=
oftware=20
> will be allowed to dynamically link against it.
>
> Cheers,
>     OdyX
Hi,

IANAL, that was only no exact proposal what can be in license file.
There is other proposal (the way how LLVM did this license change to
Apache 2.0):

---- Exceptions to the Apache 2.0 License: =E2=80=94=E2=80=94

As an exception, if you use this Software to compile your source code and=
 portions of this Software are embedded into the binary product as a resu=
lt, you may redistribute such product without providing attribution as wo=
uld otherwise be required by Sections 4(a), 4(b) and 4(d) of the License.=
 =20

In addition, if you combine or link compiled forms of this Software with =
software that is licensed under the GPLv2 (=E2=80=9CCombined Software=E2=80=
=9D) and if a court of competent jurisdiction determines that the patent =
provision (Section 3), the indemnity provision (Section 9) or other Secti=
on of the License conflicts with the conditions of the GPLv2, you may ret=
roactively and prospectively choose to deem waived or otherwise exclude s=
uch Section(s) of the License, but only in their entirety and only with r=
espect to the Combined Software.

---- end ---

Would it be acceptable for Apple, for Debian and etc.?

--=20
Zdenek Dohnal
Associate Software Engineer
Red Hat Czech - Brno TPB-C



--FLjJTWopP1hwfLPJTRsceAFnoowVD48Xh--

--3xuXi8U4rWrVVqXbqJIP8p84O6ohkvTnW--

--Boundary_(ID_gyBSUzsJC2T8b0iuVjNZMQ)
MIME-version: 1.0
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Content-disposition: inline

_______________________________________________
cups-devel mailing list
[email protected]
https://lists.cups.org/mailman/listinfo/cups-devel

--Boundary_(ID_gyBSUzsJC2T8b0iuVjNZMQ)--