From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/6] make.sh: Remove crda and remaining python2 modules
Date: Mon, 28 Jun 2021 21:13:55 +0200 [thread overview]
Message-ID: <20210628191400.2860975-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]
- crda only works with python2 version of m2crypto
python-m2crypto requires python-setuptools and python-typing
- With Linux kernel 4.15 and later the country code status check that crda did is built
into the kernel.
- So from kernel 4.15, crda can be removed, which allows removal of m2crypto, setuptools
and typing.
- python-typing is built into python3 so no additional python3 module required.
- python3 version of python-setuptools has already been installed.
- python3 version of python-m2crypto is not required. python-m2crypto is only used for the
build of crda.
- ipaddr can be removed as the function of this python2 module is built into python3 with
ipaddress.py
- removal of crda tested with 5.10.45 kernel and the setting of a country code was
recognised. If this test carried out with crda removed and 4.14.232 kernel then country
code stays defined as the global code "00".
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
make.sh | 5 -----
1 file changed, 5 deletions(-)
diff --git a/make.sh b/make.sh
index fc03ebcd5..f8767bad9 100755
--- a/make.sh
+++ b/make.sh
@@ -1307,7 +1307,6 @@ buildipfire() {
lfsmake2 whatmask
lfsmake2 libtirpc
lfsmake2 conntrack-tools
- lfsmake2 ipaddr
lfsmake2 iputils
lfsmake2 l7-protocols
lfsmake2 hwdata
@@ -1344,7 +1343,6 @@ buildipfire() {
lfsmake2 XML-Parser
lfsmake2 Crypt-PasswdMD5
lfsmake2 Net-Telnet
- lfsmake2 python-setuptools
lfsmake2 python3-setuptools
lfsmake2 python3-inotify
lfsmake2 python3-docutils
@@ -1527,10 +1525,7 @@ buildipfire() {
lfsmake2 swig
lfsmake2 u-boot
lfsmake2 u-boot-friendlyarm
- lfsmake2 python-typing
- lfsmake2 python-m2crypto
lfsmake2 wireless-regdb
- lfsmake2 crda
lfsmake2 libsolv
lfsmake2 ddns
lfsmake2 python3-setuptools-scm
--
2.32.0
next reply other threads:[~2021-06-28 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 19:13 Adolf Belka [this message]
2021-06-28 19:13 ` [PATCH 2/6] crda: removal from kernel 4.15 and onwards Adolf Belka
2021-07-09 6:26 ` Arne Fitzenreiter
2021-07-09 10:20 ` Adolf Belka
2021-07-10 7:25 ` Arne Fitzenreiter
2021-07-10 11:17 ` Adolf Belka
2021-07-11 11:29 ` Adolf Belka
2021-07-11 12:51 ` Michael Tremer
2021-07-16 12:28 ` Adolf Belka
2021-07-28 17:44 ` Adolf Belka
2021-06-28 19:13 ` [PATCH 3/6] python-m2crypto: removal of python2 module Adolf Belka
2021-06-28 19:13 ` [PATCH 4/6] python-typing: Removal of this " Adolf Belka
2021-06-28 19:13 ` [PATCH 5/6] python-setuptools: " Adolf Belka
2021-06-28 19:14 ` [PATCH 6/6] ipaddr: " Adolf Belka
2021-07-05 16:39 ` [PATCH 1/6] make.sh: Remove crda and remaining python2 modules Michael Tremer
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=20210628191400.2860975-1-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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