From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] package/nfs-utils: enable IPv6 if libtirpc is selected
Date: Tue, 10 Sep 2019 18:03:12 +0200 [thread overview]
Message-ID: <20190910180312.3e30d72f@windsurf> (raw)
In-Reply-To: <0209c0f3-3bdf-aa01-0c21-c5d775f819fc@mind.be>
On Tue, 10 Sep 2019 14:23:15 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> Oh dear, we're running in circles here...
Absolutely.
> Due to the select, all of this becomes unconditional.
>
> In other words, we should:
>
> - select libtirpc unconditionally;
> - add libtirpc to _DEPENDENCIES unconditionally;
> - add --enable-tirpc --enable-ipv6 to CONF_OPTS unconditionally;
> - leave the help text unchanged since libtirpc is anyway selected;
> - make it clear in the commit message that libtirpc is anyway selected by
> rpcbind, so we can just as well select it unconditionally in nfs-utils.
Fully agreed.
> Again, I'm very sorry that it takes us five iterations and several months to
> come to this conclusion...
Yes, indeed. But sometimes that what it takes to finally understand
each other and find what the good solution is.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-09-10 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 10:59 [Buildroot] [PATCH v4] package/nfs-utils: enable IPv6 if libtirpc is selected unixmania at gmail.com
2019-09-10 12:23 ` Arnout Vandecappelle
2019-09-10 13:07 ` Carlos Santos
2019-09-10 16:04 ` Thomas Petazzoni
2019-09-10 16:42 ` Carlos Santos
2019-09-10 16:03 ` Thomas Petazzoni [this message]
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=20190910180312.3e30d72f@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.