Re: ifupdown maintenance
- To: debian-devel@lists.debian.org
- Subject: Re: ifupdown maintenance
- From: Michael Stone <mstone@debian.org>
- Date: Sun, 15 Sep 2024 23:07:34 -0400
- Message-id: <[🔎] 6ddf561a-73d8-11ef-9b6a-00163eeb5320@msgid.mathom.us>
- Mail-followup-to: debian-devel@lists.debian.org
- In-reply-to: <20240709121326.ebogyrjk5kpuvufj@House.clients.dxld.at>
- References: <CAPZXPQdFDS4UXjvUfio7C44s22sx0hMNfDkRjmW_0zG2fep_yA@mail.gmail.com> <20240707135644.q227pfu4lg3dsqg7@House.clients.dxld.at> <CAPZXPQdvzG0e189B-5xFj5dVx=W0UpY4s0RSMHbPtovUJAdmDw@mail.gmail.com> <20240709085804.w6ox54avjne2ke3d@House.clients.dxld.at> <CAPZXPQeAT60OkvY-51jNWnGUUX4s-xWcs-f4svF73V9eEEvk_g@mail.gmail.com> <20240709121326.ebogyrjk5kpuvufj@House.clients.dxld.at>
On Tue, Jul 09, 2024 at 02:13:26PM +0200, Daniel Gröber wrote:
If ifupdown's paradigm were working for people we wouldn't be having this
conversation.
Well, the problem is that there's a selection bias in people having this
conversation--the people who are using ifupdown without issues aren't looking
for a conversation about getting rid of it, right?
How else would you move /etc/network/interfaces forward without breaking
anything?
Just don't. If someone needs to do something new that's supported by a
new tool and not ifupdown, they should just use the new tool. Freeze
ifupdown functionality, mark feature requests as wontfix, and update the
documentation.
Reply to: