All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Jose Quaresma <quaresma.jose@gmail.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH 07/17] gstreamer1.0: upgrade 1.18.5 -> 1.20.0
Date: Wed, 9 Feb 2022 19:09:50 +0000	[thread overview]
Message-ID: <dcb645fd99ba4e2ebdda348373486076@axis.com> (raw)
In-Reply-To: <20220207010823.143664-7-quaresma.jose@gmail.com>

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Jose Quaresma
> Sent: den 7 februari 2022 02:08
> To: openembedded-core@lists.openembedded.org
> Cc: Jose Quaresma <quaresma.jose@gmail.com>
> Subject: [OE-core] [PATCH 07/17] gstreamer1.0: upgrade 1.18.5 -> 1.20.0
> 
> - License update:
>   The code actually is LGPLv2.1 but the COPYING file is wrong.
>   https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/d157b23fb0ce175b167611a4cb019599d9017042

Since the COPYING file for the GStreamer sub-projects now states 
that the used license is LGPL-2.1, shouldn't the LICENSE for these 
recipes be updated to say "LGPL-2.1-or-later"?

As for -bad and -ugly, they should really have individual LICENSE:foo 
for each generated package, so that only the packages that are affected 
by the GPL license includes it, and the others only specify LGPL.

//Peter



  parent reply	other threads:[~2022-02-09 19:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  1:08 [PATCH 01/17] icecc.bbclass: replace deprecated bash command substitution Jose Quaresma
2022-02-07  1:08 ` [PATCH 02/17] spirv-headers: bump to b42ba6 Jose Quaresma
2022-02-07  1:08 ` [PATCH 03/17] spirv-tools: upgrade 2021.4 -> 2022.1 Jose Quaresma
2022-02-07  1:08 ` [PATCH 04/17] glslang: upgrade 11.7.1 -> 11.8.0 Jose Quaresma
2022-02-07  1:08 ` [PATCH 05/17] shaderc: upgrade 2021.3 -> 2021.4 Jose Quaresma
2022-02-07  1:08 ` [PATCH 06/17] shaderc: upgrade 2021.4 -> 2022.0 Jose Quaresma
2022-02-07  1:08 ` [PATCH 07/17] gstreamer1.0: upgrade 1.18.5 -> 1.20.0 Jose Quaresma
2022-02-08 22:01   ` [OE-core] " Alexander Kanavin
2022-02-09  9:15     ` Jose Quaresma
2022-02-09  9:30       ` Claudius Heine
2022-02-09 10:33         ` Alexander Kanavin
2022-02-16 23:40           ` Jose Quaresma
2022-02-17  8:27             ` Alexander Kanavin
2022-02-16 23:43         ` Jose Quaresma
2022-02-09 19:09   ` Peter Kjellerstedt [this message]
2022-02-16 23:36     ` Jose Quaresma
2022-02-07  1:08 ` [PATCH 08/17] gstreamer1.0-plugins-base: " Jose Quaresma
2022-02-07  1:08 ` [PATCH 09/17] gstreamer1.0-plugins-good: " Jose Quaresma
2022-02-07  1:08 ` [PATCH 10/17] gstreamer1.0-plugins-bad: " Jose Quaresma
2022-02-07  1:08 ` [PATCH 11/17] gstreamer1.0-plugins-ugly: " Jose Quaresma
2022-02-07  1:08 ` [PATCH 12/17] gstreamer1.0-rtsp-server: " Jose Quaresma
2022-02-07  1:08 ` [PATCH 13/17] gstreamer1.0-libav: " Jose Quaresma
2022-02-07  1:08 ` [PATCH 14/17] gstreamer1.0-vaapi: " Jose Quaresma
2022-02-07  1:08 ` [PATCH 15/17] gstreamer1.0-omx: " Jose Quaresma
2022-02-07  1:08 ` [PATCH 16/17] gstreamer1.0-python: " Jose Quaresma
2022-02-07  1:08 ` [PATCH 17/17] gst-devtools: " Jose Quaresma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dcb645fd99ba4e2ebdda348373486076@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quaresma.jose@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.