From: ecordonnier@snap.com
To: openembedded-devel@lists.openembedded.org
Cc: Etienne Cordonnier <ecordonnier@snap.com>
Subject: [meta-oe][PATCH] android-tools: drop GPL-2.0-only from LICENSE
Date: Thu, 22 Oct 2026 16:24:48 +0200 [thread overview]
Message-ID: <20261022142449.2372030-1-ecordonnier@snap.com> (raw)
From: Etienne Cordonnier <ecordonnier@snap.com>
The GPL-2.0 entry dates back to the first recipe (AOSP android-5.1.1_r37,
2016) and was carried over unchanged to the Debian android-platform-tools
based 35.0.2 recipe.
In the android-5.1.1_r37 repos the recipe fetched, the only GPLv2 mentions
are headers which are dual licensed "Apache 2.0 OR GPLv2"
(system/core include/cutils/ashmem.h, include/utils/ashmem.h,
include/log/logger.h), kernel headers in libion which are not built, and
documentation templates. Apache-2.0 can be chosen for all of them.
The 35.0.2 sources come from Debian's android-platform-tools, whose
debian/copyright lists no GPL license: the files are Apache-2.0, BSD,
Expat, Khronos, PSF and public-domain, and a scan of the unpacked tarball
finds no GPL licensed source files.
Remove GPL-2.0-only from LICENSE and LIC_FILES_CHKSUM so that the recipe is
not wrongly treated as GPL by license based tooling (e.g. copyleft source
archiving).
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
---
meta-oe/recipes-devtools/android-tools/android-tools_35.0.2.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta-oe/recipes-devtools/android-tools/android-tools_35.0.2.bb b/meta-oe/recipes-devtools/android-tools/android-tools_35.0.2.bb
index 65529c1b53..b7cb062410 100644
--- a/meta-oe/recipes-devtools/android-tools/android-tools_35.0.2.bb
+++ b/meta-oe/recipes-devtools/android-tools/android-tools_35.0.2.bb
@@ -1,9 +1,8 @@
DESCRIPTION = "Various utilities from Android"
SECTION = "console/utils"
-LICENSE = "Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND GPL-2.0-only"
+LICENSE = "Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause"
LIC_FILES_CHKSUM = " \
file://${COMMON_LICENSE_DIR}/Apache-2.0;md5=89aea4e17d99a7cacdbeed46a0096b10 \
- file://${COMMON_LICENSE_DIR}/GPL-2.0-only;md5=801f80980d171dd6425610833a22dbe6 \
file://${COMMON_LICENSE_DIR}/BSD-2-Clause;md5=cb641bc04cda31daea161b1bc15da69f \
file://${COMMON_LICENSE_DIR}/BSD-3-Clause;md5=550794465ba0ec5312d6919e203a55f9 \
"
--
2.43.0
reply other threads:[~2026-10-22 14:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261022142449.2372030-1-ecordonnier@snap.com \
--to=ecordonnier@snap.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox