From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH v2 1/8] make.sh: Remove crda and remaining python2 modules
Date: Wed, 28 Jul 2021 19:29:25 +0200 [thread overview]
Message-ID: <20210728172932.2737967-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 13a48f461..57b83e432 100755
--- a/make.sh
+++ b/make.sh
@@ -1296,7 +1296,6 @@ buildipfire() {
lfsmake2 whatmask
lfsmake2 libtirpc
lfsmake2 conntrack-tools
- lfsmake2 ipaddr
lfsmake2 iputils
lfsmake2 l7-protocols
lfsmake2 hwdata
@@ -1333,7 +1332,6 @@ buildipfire() {
lfsmake2 XML-Parser
lfsmake2 Crypt-PasswdMD5
lfsmake2 Net-Telnet
- lfsmake2 python-setuptools
lfsmake2 python3-setuptools
lfsmake2 python3-inotify
lfsmake2 python3-docutils
@@ -1517,10 +1515,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-07-28 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 17:29 Adolf Belka [this message]
2021-07-28 17:29 ` [PATCH v2 2/8] crda: removal from kernel 4.15 and onwards Adolf Belka
2021-07-28 17:29 ` [PATCH v2 3/8] python-m2crypto: removal of python2 module Adolf Belka
2021-07-28 17:29 ` [PATCH v2 4/8] python-typing: Removal of this " Adolf Belka
2021-07-28 17:29 ` [PATCH v2 5/8] python-setuptools: " Adolf Belka
2021-07-28 17:29 ` [PATCH v2 6/8] ipaddr: " Adolf Belka
2021-07-28 17:29 ` [PATCH v2 7/8] wireless-regdb: Use db.txt file for wlanap.cgi Adolf Belka
2021-08-04 14:34 ` Michael Tremer
2021-07-28 17:29 ` [PATCH v2 8/8] wlanap.cgi: Access db.txt in place of using regdbdump on regulatory.bin Adolf Belka
2021-08-04 14:32 ` Michael Tremer
2021-08-04 17:04 ` Adolf Belka
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=20210728172932.2737967-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