Re: [cups-devel] CUPS License Change Coming
Zdenek Dohnal <[email protected]> Fri, 1 Dec 2017 08:12:23 +0100
| Newsgroups | gmane.comp.printing.cups.devel |
|---|---|
| Message-ID | <[email protected]> |
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Boundary_(ID_KiLdu1qnAsddNnbDrn20kw) Content-type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary=XLxLmWDGVngmLITHOkdbRBIBOC3uSI9o0 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XLxLmWDGVngmLITHOkdbRBIBOC3uSI9o0 Content-Type: multipart/mixed; boundary="GDbtPU9lCvUMLGbABgHi5IndU3pF6K9Ll"; protected-headers="v1" From: Zdenek Dohnal <[email protected]> To: [email protected] Cc: Michael Sweet <[email protected]> Message-ID: <05636026-dd2d-128e-24dd-c6974612b930-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Subject: Re: [cups-devel] CUPS License Change Coming References: <2E55FEEC-11BA-4789-B6F8-C6CCC27A8884-2kanFRK1NckAvxtiuMwx3w@public.gmane.org> <[email protected]> <BC8ED8CE-941C-4F90-94D3-045CCD2123D5-2kanFRK1NckAvxtiuMwx3w@public.gmane.org> <3aae6aa4-f4e5-c8f8-f1bf-dc3c3f718c87-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> <FE4BA9E2-056A-44C5-9C8F-97D0D3F4580B-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> <DDDCF9C8-5466-4BF7-9C94-EFF620B13A00-2kanFRK1NckAvxtiuMwx3w@public.gmane.org> In-Reply-To: <DDDCF9C8-5466-4BF7-9C94-EFF620B13A00-2kanFRK1NckAvxtiuMwx3w@public.gmane.org> --GDbtPU9lCvUMLGbABgHi5IndU3pF6K9Ll Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US On 11/30/2017 05:49 PM, Michael Sweet wrote: > Thanks, I'll forward this internally at Apple. Our intent is that > everyone can use and link to CUPS, and our assumption is (based on the > fact that CUPS is part of most every OS except Windows) that > libcups/libcupsimage qualify as system-supplied libraries for the > purposes of the GPLv2/LGPLv2. > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > You're right, e.g. if you are saying the libcups is compatible with GPLv2/LGPLv2 because libcups is OS-supplied library, then it is okay to link libcups to my software, if I see it compatible too, because intents of both upstreams matters. (Actually, I don't see reason for other upstream will see it incompatible - maybe when they have a policy in which is said Apache2.0+GPLv2 is not compatible, but I don't recall there is someone like that) --=20 Zdenek Dohnal Associate Software Engineer Red Hat Czech - Brno TPB-C --GDbtPU9lCvUMLGbABgHi5IndU3pF6K9Ll-- --XLxLmWDGVngmLITHOkdbRBIBOC3uSI9o0-- --Boundary_(ID_KiLdu1qnAsddNnbDrn20kw) 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_KiLdu1qnAsddNnbDrn20kw)--