From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: should we make --enable-tirpc the default in current nfs-utils?
Date: Fri, 5 Jun 2009 12:38:28 -0400 [thread overview]
Message-ID: <20090605163828.GG10975@fieldses.org> (raw)
In-Reply-To: <4D090F4F-4063-429C-829B-E56A1B127D3B@oracle.com>
On Fri, Jun 05, 2009 at 12:14:48PM -0400, Chuck Lever wrote:
>
> On Jun 5, 2009, at 12:10 PM, J. Bruce Fields wrote:
>
>> On Fri, Jun 05, 2009 at 07:36:48AM -0400, Jeff Layton wrote:
>>> Eventually, we most distros are going to want to build nfs-utils
>>> against libtirpc in order to get IPv6 support. At some point, we'll
>>> probably want to make building with IPv6 support the default. In the
>>> meantime however, we need to get more testing exposure for the TI-RPC
>>> codepaths. We'll probably start building Fedora's nfs-utils with TI-
>>> RPC
>>> support in the near future.
>>>
>>> The question that Steve D. has asked is whether we should also make
>>> --enable-tirpc the default for the mainline nfs-utils tree?
>>>
>>> Doing this now would add wider testing exposure for these codepaths
>>> and
>>> help flush out bugs in TIRPC+IPV4 codepaths. OTOH, it means adding a
>>> new library dependency for packagers, or they'll need to take the
>>> conscious step to --disable-tirpc when they configure.
>>>
>>> We could make it so that configure looks for libtirpc and if it's not
>>> available, configures the build against legacy RPC interfaces. I
>>> think
>>> this is a bad idea however. While it should "just work" either way,
>>> there are some small behavioral differences when TIRPC support is
>>> built
>>> in. I think it's probably better to make enabling and disabling
>>> TIRPC a
>>> conscious step.
>>>
>>> Thoughts?
>>
>> Makes sense to me to have upstream defaults set to what we expect
>> distributions to move to, assuming there aren't known regressions.
>
> That's a big assumption,
I'm confused--there are known regressions or there aren't. (I'm not
talking about unknown regressions....)
> and it's exactly why we wanted to have some soak time in rawhide or
> Debian unstable before enabling it by default upstream.
I don't think upstream needs to be more conservative than the
development distro's.
--b.
next prev parent reply other threads:[~2009-06-05 16:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 11:36 should we make --enable-tirpc the default in current nfs-utils? Jeff Layton
[not found] ` <20090605073648.5a5497b5-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-05 16:10 ` J. Bruce Fields
2009-06-05 16:14 ` Chuck Lever
2009-06-05 16:38 ` J. Bruce Fields [this message]
2009-06-05 17:30 ` Chuck Lever
2009-06-05 18:14 ` Steve Dickson
2009-06-05 16:24 ` Mike Frysinger
2009-06-05 17:36 ` Jeff Layton
[not found] ` <20090605133634.23357e8e-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-05 20:50 ` Mike Frysinger
2009-06-06 11:11 ` Jeff Layton
[not found] ` <20090606071153.164d92dd-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-06 18:00 ` Muntz, Daniel
[not found] ` <7A24DF798E223B4C9864E8F92E8C93EC031D19D3-hX7t0kiaRRpT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2009-06-06 20:02 ` Jeff Layton
[not found] ` <20090606160230.247d3ca3-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-08 9:09 ` Steve Dickson
[not found] ` <4A2CD550.4090609-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-08 11:10 ` Jeff Layton
[not found] ` <20090608071026.0b57fff8-PC62bkCOHzGdMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2009-06-08 13:36 ` Steve Dickson
[not found] ` <4A2D13DF.2040105-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-08 14:26 ` Chuck Lever
2009-06-08 15:04 ` Steve Dickson
[not found] ` <4A2D2862.3090303-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-08 15:24 ` Chuck Lever
2009-06-08 16:41 ` Jeff Layton
[not found] ` <20090608124140.3fa02688-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-08 16:50 ` Chuck Lever
2009-06-08 17:00 ` Jeff Layton
[not found] ` <20090608130012.0bea6215-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-08 17:36 ` Chuck Lever
2009-06-09 12:06 ` Steve Dickson
[not found] ` <4A2E503E.1080809-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-09 14:30 ` Chuck Lever
2009-06-09 14:48 ` Steve Dickson
[not found] ` <4A2E7646.1030602-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-09 15:29 ` Chuck Lever
2009-06-09 15:41 ` Steve Dickson
[not found] ` <4A2E82AD.7070908-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-09 17:01 ` Chuck Lever
2009-06-08 14:16 ` Chuck Lever
2009-06-08 14:23 ` Mike Frysinger
2009-06-08 15:36 ` Muntz, Daniel
[not found] ` <7A24DF798E223B4C9864E8F92E8C93EC031D1B02-hX7t0kiaRRpT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2009-06-08 16:49 ` Jeff Layton
[not found] ` <20090608124913.7340074c-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-09 12:58 ` Steve Dickson
2009-06-08 15:46 ` Muntz, Daniel
[not found] ` <7A24DF798E223B4C9864E8F92E8C93EC031D1B12-hX7t0kiaRRpT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2009-06-08 16:59 ` Jeff Layton
[not found] ` <20090608125957.3c8f0c95-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-08 17:05 ` Chuck Lever
2009-06-08 17:10 ` Jeff Layton
[not found] ` <20090608131024.6aa0c020-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-06-08 17:46 ` Chuck Lever
2009-06-09 12:35 ` Steve Dickson
[not found] ` <4A2E5714.3030502-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-06-09 14:48 ` Chuck Lever
2009-06-09 15:27 ` Steve Dickson
2009-06-08 22:17 ` Muntz, Daniel
[not found] ` <7A24DF798E223B4C9864E8F92E8C93EC031D1EFD-hX7t0kiaRRpT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2009-06-08 23:08 ` Jeff Layton
[not found] ` <20090608190825.046355d4-PC62bkCOHzGdMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2009-06-09 1:41 ` Muntz, Daniel
2009-06-09 13:18 ` Steve Dickson
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=20090605163828.GG10975@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.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