From: Chuck Lever <chuck.lever@oracle.com>
To: Mark Liam Brown <brownmarkliam@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: libxml/GNOME dependency MADNESS cleanup: nfsref(8) removal
Date: Thu, 22 May 2025 12:00:28 -0400 [thread overview]
Message-ID: <45bf7584-7dd6-47ce-9a51-fe47e6ebc5a9@oracle.com> (raw)
In-Reply-To: <CAN0SSYw8j-nyObz_F6C13sOntap-JYRNDusx+M8_WHzfPH-KmQ@mail.gmail.com>
On 5/22/25 11:58 AM, Mark Liam Brown wrote:
> Greetings!
>
> I am going to post a patch series to remove the nfsref(8) utility.
>
> So far the "utility" has only created more harm (namely, dragging in
> GNOME(!!!!!) libxml and cohorts dependencies, and related dependency
> breakage, which in itself is INTOLERABLE; and breaking NFS root
> support); and only obscure "benefits" (NFS referrals, which no one
> uses).
>
> Following that will be a patch series for Kconfig to make NFS referral
> support optional, and then mark them as depreciated.
>
> Mark
NACK.
--
Chuck Lever
next prev parent reply other threads:[~2025-05-22 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 15:58 libxml/GNOME dependency MADNESS cleanup: nfsref(8) removal Mark Liam Brown
2025-05-22 16:00 ` Chuck Lever [this message]
2025-05-29 14:23 ` Jeff Layton
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=45bf7584-7dd6-47ce-9a51-fe47e6ebc5a9@oracle.com \
--to=chuck.lever@oracle.com \
--cc=brownmarkliam@gmail.com \
--cc=linux-nfs@vger.kernel.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