From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: connman: build with --enable-iwd, add build option "nftables", split openconnect plugin, remove runtime dependency on wpa_supplicant
Date: Thu, 09 Jun 2022 04:11:19 +0200 [thread overview]
Message-ID: <20220609021119.aQ2HYQByGXKEoqMtAL1K168EuOMcwBxrcqWDTuJbGeY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31916@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
There's a closed pull request on the void-packages repository
connman: build with --enable-iwd, add build option "nftables", split openconnect plugin, remove runtime dependency on wpa_supplicant
https://github.com/void-linux/void-packages/pull/31916
Description:
1. Build with --enable-iwd
iwd is a better alternative to wpa_supplicant.
1. Add build option "nftables"
Allow to build with support for nftables instead of iptables.
From ./configure --help:
--with-firewall=TYPE specify which firewall type is used iptables or
nftables [default=iptables]
1. Split openconnect plugin into subpackage
OpenConnect VPN is not widely used and it adds many dependencies to the connman package. On my system, removing openconnect orphaned the following packages: openconnect trousers vpnc-scripts libpcsclite mit-krb5-libs with total size over 5 MiB.
1. Remove runtime dependency on wpa_supplicant
ConnMan can be used with iwd or even without any WiFi program, because it can be used for Ethernet devices.
1. Split openvpn and wireguard to subpackages
The main motivation to split openvpn into a subpackage is to correctly declare its dependency on "openvpn" package. Wireguard doesn't seem to depend on any other package, that's just for consistency with other VPN plugins.
prev parent reply other threads:[~2022-06-09 2:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 22:29 [PR PATCH] connman: build with --enable-iwd jirutka
2021-07-12 5:33 ` ericonr
2021-07-12 8:31 ` jirutka
2021-07-14 13:48 ` [PR PATCH] [Updated] " jirutka
2021-07-14 13:49 ` connman: build with --enable-iwd, add build option "nftables" ericonr
2021-07-14 13:52 ` jirutka
2021-07-14 22:59 ` [PR PATCH] [Updated] " jirutka
2021-07-15 23:45 ` [PR PATCH] [Updated] connman: build with --enable-iwd, add build option "nftables", split openconnect plugin, remove runtime dependency on wpa_supplicant jirutka
2021-07-15 23:47 ` jirutka
2021-07-16 21:01 ` jirutka
2021-07-17 3:11 ` ericonr
2021-07-17 3:25 ` ahesford
2021-07-17 3:32 ` abenson
2022-05-25 2:15 ` github-actions
2022-06-09 2:11 ` github-actions [this message]
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=20220609021119.aQ2HYQByGXKEoqMtAL1K168EuOMcwBxrcqWDTuJbGeY@z \
--to=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).