From: Aniket Limaye <a-limaye@ti.com>
To: <meta-arago@lists.yoctoproject.org>
Cc: <reatmon@ti.com>, Aniket Limaye <a-limaye@ti.com>
Subject: [meta-arago][master/kirkstone][PATCH] arago-gpl-notice: Update script to look for updated GPL-3.0 identifier
Date: Wed, 4 Oct 2023 12:11:20 +0530 [thread overview]
Message-ID: <20231004064120.704114-1-a-limaye@ti.com> (raw)
The license identifier was updated from GPLv3 to GPL-3.0
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
---
.../arago-gpl-notice/print-gplv3-packages.sh | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta-arago-distro/recipes-core/arago-gpl-notice/arago-gpl-notice/print-gplv3-packages.sh b/meta-arago-distro/recipes-core/arago-gpl-notice/arago-gpl-notice/print-gplv3-packages.sh
index 08cb3b4a..a47773f0 100644
--- a/meta-arago-distro/recipes-core/arago-gpl-notice/arago-gpl-notice/print-gplv3-packages.sh
+++ b/meta-arago-distro/recipes-core/arago-gpl-notice/arago-gpl-notice/print-gplv3-packages.sh
@@ -19,9 +19,9 @@
gplv3_packages=""
-# find all files with GPLv3 in them that do not also have RLE
+# find all files with GPL-3.0 in them that do not also have RLE
# exception listed.
-files=`grep License: /var/lib/opkg/info/*.control | grep -i GPLv3 | grep -v RLE | cut -d: -f1 | sort -u`
+files=`grep License: /var/lib/opkg/info/*.control | grep -i GPL-3.0 | grep -v RLE | cut -d: -f1 | sort -u`
for i in $files
do
@@ -36,11 +36,11 @@ then
cat << EOM 2>&1
***************************************************************
***************************************************************
-NOTICE: This file system contains the following GPLv3 packages:
+NOTICE: This file system contains the following GPL-3.0 packages:
EOM
echo -e $gplv3_packages 2>&1
cat << EOM 2>&1
-If you do not wish to distribute GPLv3 components please remove
+If you do not wish to distribute GPL-3.0 components please remove
the above packages prior to distribution. This can be done using
the opkg remove command. i.e.:
opkg remove <package>
--
2.34.1
reply other threads:[~2023-10-04 6:41 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=20231004064120.704114-1-a-limaye@ti.com \
--to=a-limaye@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=reatmon@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).