Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: iproute2: move usr/bin/tc to -tc-ipt subpackage
Date: Fri, 10 Jun 2022 04:13:27 +0200	[thread overview]
Message-ID: <20220610021327.2QFSRLnVvuXAEMI1X4y5InRjfH_ItLVbiWvtyV0j4nw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31961@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2062 bytes --]

There's a closed pull request on the void-packages repository

iproute2: move usr/bin/tc to -tc-ipt subpackage
https://github.com/void-linux/void-packages/pull/31961

Description:
/usr/bin/tc is used to configure Traffic Control, it should be part of existing iproute2-tc-ipt subpackage.

The primary motivation to move /usr/bin/tc into subpackage is to remove dependency on iptables package in iproute2, and transitively from base-system. Users who use nftables instead of legacy iptables would not have to blacklist iptables package anymore.

**IMPORTANT**: base-system doesn’t directly depend on iptables, but it depends on iproute2, so iptables is installed by default. It’s described in the [Firewalls documentation](https://docs.voidlinux.org/config/network/firewalls.html):

> By default, the iptables package is installed on the base system. It provides iptables(8)/ip6tables(8). The related services use the /etc/iptables/iptables.rules and /etc/iptables/ip6tables.rules ruleset files, which must be created by the system administrator.

I think that pulling iptables with the base-system by default is wrong. nftables is clearly superior and should be preferred on new installations. I don’t mean that it should be forced, just that iptables should not be the default. Since base-system is supposed to contain really just a base system (there’s not even a cron or syslog included), I think that it should not directly depend on iptables nor nftables.

However, many users probably rely on iptables being installed as transitive dependency of base-system, so effectively removing it from the dependency graph may cause troubles.

What can we do?

a) Inform users about the change, e.g. in post-upgrade message?
a.1) Can we automatically mark iptables as explicit dependency via hook when upgrading iproute2?
b) Add dependency on iptables to the base-system package (lowest effort).
c) Maybe create a virtual _firewall_ and make base-system depend on it? However, I don’t know yet how this works in xbps.
d) …?

/cc @q66 

  parent reply	other threads:[~2022-06-10  2:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 14:41 [PR PATCH] " jirutka
2021-07-14 14:48 ` q66
2021-11-24 16:28 ` leahneukirchen
2021-11-24 16:34 ` leahneukirchen
2022-05-26  2:13 ` github-actions
2022-06-10  2:13 ` github-actions [this message]
2023-05-31 16:23 ` charwhee

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=20220610021327.2QFSRLnVvuXAEMI1X4y5InRjfH_ItLVbiWvtyV0j4nw@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).