From: Khem Raj <raj.k...@gmail.com> Sent: Sunday, May 5, 2024 21:22 To: Marko, Peter (ADV D EU SK BFS1) <peter.ma...@siemens.com> Cc: openembedded-core@lists.openembedded.org Subject: Re: [OE-core][PATCH] glibc: correct license
> On Sun, May 5, 2024 at 2:18 AM Peter Marko via http://lists.openembedded.org > <peter.marko=mailto:siemens....@lists.openembedded.org> wrote: > > From: Peter Marko <mailto:peter.ma...@siemens.com> > > > > The license per https://www.gnu.org/software/libc/ is LGPL-2.1-or-later. > > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=273a835fe7c685cc54266bb8b502787bad5e9bae > > converted last LGPL-2.1-only references. > > > > License-Update: correction > > This should reflect reason but overall the patch is ok > Could you please be more specific what should I write? The long reason is written above the License-Update field, I just added the field to satisfy the patch checker bot. Putting the whole text to this field doesn't look right. I don't know the history of glibc license to be able to assess if they migrated recently or if these were just wrongly committed licenses. I just noticed the commit when updating glibc to the latest hash and decided to correct the recipe LICENSE field according to this hint. So "correction" looks to me like a good short statement wrt the recipe LICENSE field. Thanks, Peter
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#199026): https://lists.openembedded.org/g/openembedded-core/message/199026 Mute This Topic: https://lists.openembedded.org/mt/105919323/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
