Re: [cups-devel] CUPS License Change Coming
Solomon Peachy <[email protected]> Wed, 8 Nov 2017 15:21:34 -0500
| Newsgroups | gmane.comp.printing.cups.devel |
|---|---|
| Message-ID | <[email protected]> |
--Boundary_(ID_C8dlnf12rWepXsF/bdx/7A) Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=zH41lVBEV8cLJnCl Content-disposition: inline --zH41lVBEV8cLJnCl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 08, 2017 at 02:58:37PM -0500, Michael Sweet wrote: > IANAL and am not comfortable getting into a legal debate about what=20 > constitutes an OS-supplied library or whether GPL2-only software can=20 > "legally" link against libcups. But as an example, CUPS had to deal=20 > with this when linking against OpenSSL in the past by adding an=20 > exception to the license file saying "it is OK to link CUPS against=20 > OpenSSL"... I don't see why that approach would not work for any=20 > GPLv2-only project, if there was any question about CUPS being a=20 > standard OS library after almost 20 years of use... I don't want to get into a debate here either, but suffice it to say=20 that it's not entirelty clear whether or not the "OS Exception" to the=20 GPLv2 applies to other parts of the same operating system. (ie, a=20 typical Linux distribution) Gutenprint (GPLv2+) is one of those projects impacted by this; our CUPS=20 filters obviously link against libcups today, but this also impacts=20 future plans -- for example that IPP proof-of-concept you and I recently=20 discussed. Gutenprint had plans to more tightly integrate CUPS into=20 our foundational libraries. We're still evaluating what this will mean. > Anyways, I can certainly forward your dual-licensing request to the=20 > appropriate people at Apple, but I'm sure they will want to know which=20 > projects/applications you think will be unable to continue using CUPS,=20 > and why. If you're going to pass the request to the powers that be at Apple, IMO=20 it would make more sense for the two licenses to be ASL2.0 and LGPLv2=20 (or better yet, LGPLv2+). That would yield the widest compatibility=20 with other/existing projects. Thanks, - Solomon --=20 Solomon Peachy pizza at shaftnet dot org Coconut Creek, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum videtur. --zH41lVBEV8cLJnCl-- --Boundary_(ID_C8dlnf12rWepXsF/bdx/7A) 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_C8dlnf12rWepXsF/bdx/7A)--