Hi Martin, license handling is a very complicated topic, especially for historical projects like glibc with ton of files with diverse origin. License scanning programs will find 15+ different licenses here and some of them may not be even available in yocto license list. I submitted this particular commit because I was responsible for an update with commit which was asking for it.
The discussion you linked about adding SPDX identifiers is something which would really help. It would enable license discovery without need of big data software and allow to accurately set the LICENSE field also by SW developers. Peter -----Original Message----- From: Martin Jansa <martin.ja...@gmail.com> Sent: Thursday, May 16, 2024 7:30 To: Marko, Peter (ADV D EU SK BFS1) <peter.ma...@siemens.com> Cc: openembedded-core@lists.openembedded.org Subject: Re: [OE-core][PATCH v2] glibc: correct license > Hi Peter, > > what about BSD-4-Clause-UC, BSD-3-Clause, ISC licenses included in glibc. > > I've suggested to add them long time ago in: > https://lists.openembedded.org/g/openembedded-core/topic/91285771#msg166005 > which resulted in: > https://sourceware.org/bugzilla/show_bug.cgi?id=28007 > https://sourceware.org/pipermail/libc-alpha/2022-May/139167.html > but the discussion upstream stopped shortly after and the oe-core change was > never merged because of that. Maybe it's time to re-check and ping upstream > again after 2 years. > > Cheers, > > On Mon, May 6, 2024 at 9:46 AM Peter Marko via lists.openembedded.org > <peter.marko=siemens....@lists.openembedded.org> wrote: > ...
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#199496): https://lists.openembedded.org/g/openembedded-core/message/199496 Mute This Topic: https://lists.openembedded.org/mt/105935723/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
