All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Jan Engelhardt <ej@inai.de>
Cc: Arturo Borrero Gonzalez <arturo@debian.org>,
	Duncan Roe <duncan_roe@optusnet.com.au>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Jan Engelhardt <jengelh@inai.de>,
	netfilter-devel@vger.kernel.org, fw@strlen.de,
	matthias.gerstner@suse.com, eric@garver.life
Subject: Re: [PATCH] tools: add a systemd unit for static rulesets
Date: Sun, 23 Mar 2025 22:04:08 +0100	[thread overview]
Message-ID: <Z-B3SLFZMoZmZObv@orbyte.nwl.cc> (raw)
In-Reply-To: <s44sopr8-7n17-1979-4qrr-4p5ps9s4s1rn@vanv.qr>

On Sun, Mar 23, 2025 at 02:34:01PM +0100, Jan Engelhardt wrote:
> 
> On Sunday 2025-03-23 11:00, Arturo Borrero Gonzalez wrote:
> >> On Saturday 2025-03-22 02:49, Duncan Roe wrote:
> >>>>
> >>>> I have mixed feelings about having this systemd service file in this
> >>>> repository.
> >>>> Will this file be maintained wrt. systemd ecosystem updates? Or will it be
> >>>> outdated and neglected after a few years?
> >> 
> >> There are no changes expected to be necessary.
> >
> > How so? Is the systemd ecosystem not evolving?
> 
> I do not have a crystal ball that shows me what will (or will not)
> happen in the future, so as far as I can tell, it is perfect as it is.
> And I have no indication that unit files are planned to be ditched
> anytime soon.

Even if things will change and this thing gets outdated, who cares? The
bottom line is what we do currently, namely maintain nftables.service
ourselves downstream.

Apart from having to deal with heated debates over its content on the ML
there is no real burden for upstream to maintain it, either.

To me, this is an opportunity to share knowledge (e.g. others performing
a needed unit file update before I find time reading up on systemd's
latest "invention") and it may even encourage downstream maintainers in
collecting/discussing sample config best practices.

Cheers, Phil

  reply	other threads:[~2025-03-23 21:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 20:59 [PATCH] tools: add a systemd unit for static rulesets Jan Engelhardt
2025-03-05 21:35 ` Pablo Neira Ayuso
2025-03-21 13:29   ` Arturo Borrero Gonzalez
2025-03-22  1:49     ` Duncan Roe
2025-03-22  9:24       ` Jan Engelhardt
2025-03-23 10:00         ` Arturo Borrero Gonzalez
2025-03-23 13:34           ` Jan Engelhardt
2025-03-23 21:04             ` Phil Sutter [this message]
2025-03-23 10:24     ` Pablo Neira Ayuso
2025-03-06 14:16 ` Eric Garver
2025-03-20 14:05   ` Phil Sutter
2025-03-22  9:46     ` Jan Engelhardt
2025-03-25  1:34     ` Dan Winship
2025-03-26 15:56       ` Phil Sutter
2025-03-26 22:21         ` Jan Engelhardt
2025-04-17 12:39           ` Pablo Neira Ayuso
2025-03-27 11:12         ` Dan Winship
2025-03-27 13:29           ` Phil Sutter
2025-03-22  9:41   ` Jan Engelhardt

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=Z-B3SLFZMoZmZObv@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=arturo@debian.org \
    --cc=duncan_roe@optusnet.com.au \
    --cc=ej@inai.de \
    --cc=eric@garver.life \
    --cc=fw@strlen.de \
    --cc=jengelh@inai.de \
    --cc=matthias.gerstner@suse.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.