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: nfs-utils library dependency littering - fork nfs-utils for Debian? Re: [patch] mount.nfs: Add support for nfs://-URLs ...
Date: Fri, 6 Dec 2024 11:58:48 -0500 [thread overview]
Message-ID: <15b348d5-abfa-49cf-b605-3819feecc340@oracle.com> (raw)
In-Reply-To: <CAN0SSYyzWqp2CMziwQ9dGQ8X4+cL42P78oLZDZDrxbPTK_racQ@mail.gmail.com>
On 12/6/24 11:15 AM, Mark Liam Brown wrote:
> On Fri, Dec 6, 2024 at 4:54 PM Chuck Lever <chuck.lever@oracle.com> wrote:
>> IMO, using a URL parser library might be better for us in the
>> long run (eg, more secure) than adding our own little
>> implementation. FedFS used liburiparser.
>
> Yeah, another library dependency for Debian? First you try to invade
> Debian with libxml2 via backdoor, and now you try to add liburlparser?
> At that point I would suggest that Debian just forks nfs-utils and
> yanks the whole libxml&liburlparser garbage out and replace it with a
> simple line parser. Does the same job and doesn't litter Debian
This is a political screed rather than a technical concern. For one
thing, a fork certainly isn't needed to remove libxml2 or any other
library dependency -- all distributors carry local patches to such
packages.
In any event, I had thought that the Linux community preferred to
de-duplicate common functionality like this. If distributions want a
less secure, harder-to-maintain solution, then they are welcome to
speak up and explain themselves. That's what the review process is for.
--
Chuck Lever
next prev parent reply other threads:[~2024-12-06 16:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 10:54 [patch] mount.nfs: Add support for nfs://-URLs Roland Mainz
2024-12-06 15:54 ` Chuck Lever
2024-12-06 16:15 ` nfs-utils library dependency littering - fork nfs-utils for Debian? " Mark Liam Brown
2024-12-06 16:58 ` Chuck Lever [this message]
2024-12-06 17:13 ` Mark Liam Brown
2024-12-06 19:40 ` Chuck Lever
2024-12-06 23:33 ` Roland Mainz
2024-12-07 15:20 ` Chuck Lever
2024-12-07 20:29 ` Chuck Lever
2024-12-19 14:47 ` Cedric Blancher
2024-12-07 20:53 ` NeilBrown
2024-12-07 22:54 ` Chuck Lever
2024-12-08 3:29 ` NeilBrown
2024-12-08 15:58 ` Chuck Lever
2024-12-09 15:15 ` Takeshi Nishimura
2024-12-09 15:46 ` Chuck Lever
2024-12-08 7:31 ` patchwork instance for linux-nfs patches? Cedric Blancher
2024-12-08 16:01 ` Chuck Lever
2024-12-08 7:41 ` [patch] mount.nfs: Add support for nfs://-URLs Cedric Blancher
2024-12-08 16:43 ` Chuck Lever
2024-12-10 11:46 ` Benjamin Coddington
2024-12-10 12:09 ` Steve Dickson
2024-12-07 17:05 ` Takeshi Nishimura
2024-12-08 22:12 ` NeilBrown
2024-12-10 12:13 ` Cedric Blancher
2024-12-10 14:15 ` Chuck Lever
2024-12-11 4:26 ` NeilBrown
2024-12-19 14:03 ` Cedric Blancher
2024-12-24 22:59 ` NeilBrown
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=15b348d5-abfa-49cf-b605-3819feecc340@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