From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0EE4C384F017; Mon, 30 May 2022 15:04:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0EE4C384F017 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/28007] Add SPDX license identifiers Date: Mon, 30 May 2022 15:04:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc flagtypes.name Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2022 15:04:44 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28007 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com Flags| |security- --- Comment #6 from Florian Weimer --- (In reply to richard.purdie from comment #4) > I would love to see this as it would significantly improve license > identifier coverage of our code. Yocto Project uses the debug symbol/file > information to work out which files contribute to a given binary and if > those have SPDX identifiers, we can give a reasonable indication of t= he > license for the binary. Why is this important to you? The bulk of glibc is under the LGPL. Providing just an SPDX identifier does= not comply with the LGPL notification requirements, and requirements to provide source code and enable relinking. Even the glibc parts not licensed under t= he LGPL (as far as they even exist) were originally released under licenses th= at have notification requirements. You need to include the entire notices, not just SPDX identifiers, and presently the only way to do this is to include = the entire source code. These permissive licenses typically say =E2=80=9Cprovid= ed that the above copyright notice and this permission notice appear in all copies=E2=80=9D o= r =E2=80=9Cmust retain the above copyright notice, this list of conditions and the following disclaimer=E2=80=9D, and not =E2=80=9Cprovided that you include an SPDX ide= ntifier for a text substantially similar to this notice=E2=80=9D. Without better understanding the use case, I don't think it's a good idea to spend glibc project resources on figuring out what the appropriate SPDX identifier for a file like resolv/res_query.c or resolv/compat-gethnamaddr.c should be. --=20 You are receiving this mail because: You are on the CC list for the bug.=