mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] openvpn: enable iproute2
Date: Fri, 5 Jun 2020 11:53:28 +0200	[thread overview]
Message-ID: <20200605095328.GA1716@pengutronix.de> (raw)
In-Reply-To: <20200605092757.GA1321273@lenoch>

On Fri, Jun 05, 2020 at 11:27:57AM +0200, Ladislav Michl wrote:
> On Fri, Jun 05, 2020 at 10:41:37AM +0200, Michael Olbrich wrote:
> > On Thu, Jun 04, 2020 at 08:32:40AM +0200, Ladislav Michl wrote:
> > > Use (rt)netlink interface provided by 'ip' tool by default.
> > > 
> > > Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> > > ---
> > >  rules/openvpn.in   | 13 +++++++------
> > >  rules/openvpn.make |  2 +-
> > >  2 files changed, 8 insertions(+), 7 deletions(-)
> > > 
> > > diff --git a/rules/openvpn.in b/rules/openvpn.in
> > > index 6958e2940..afa124e10 100644
> > > --- a/rules/openvpn.in
> > > +++ b/rules/openvpn.in
> > > @@ -9,11 +9,10 @@ menuconfig OPENVPN
> > >  	select IPTABLES			if OPENVPN_INSTALL_SAMPLE_CONFIGS && RUNTIME
> > >  	select IPTABLES_INSTALL_TOOLS	if OPENVPN_INSTALL_SAMPLE_CONFIGS && RUNTIME
> > >  	select BRIDGE_UTILS		if OPENVPN_INSTALL_SAMPLE_SCRIPTS && RUNTIME
> > > -	select IPROUTE2			if !BUSYBOX_IP && RUNTIME
> > > -	select IPROUTE2_IP		if !BUSYBOX_IP && RUNTIME
> > > -	select BUSYBOX_IFCONFIG		if RUNTIME
> > > -	select BUSYBOX_NETSTAT		if RUNTIME
> > > -	select BUSYBOX_ROUTE		if RUNTIME
> > > +	select BUSYBOX_FEATURE_IP_LINK	if BUSYBOX_IP && RUNTIME
> > > +	select BUSYBOX_FEATURE_IP_ROUTE	if BUSYBOX_IP && RUNTIME
> > > +	select IPROUTE2			if !BUSYBOX && RUNTIME
> > > +	select IPROUTE2_IP		if !BUSYBOX && RUNTIME
> > 
> > Why not just leave the !BUSYBOX_IP here? Then the comment below is not
> > needed because either IPROUTE2_IP or IPROUTE2_IP will be selected.
> 
> We need to select A or B, but there is no simple way of doing this.
> When BUSYBOX is not used, then IPROUTE2_IP is the only option, but
> with BUSYBOX selected, that leads to IPROUTE2_IP being silently selected.
> This way user is warned about pulling another package and can act
> accordingly.

That's ok, we silently select packages all the time :-).

> Note that we cannot select BUSYBOX_IP anyway (circular dependency),
> so this is at least consistent :-)

Yes I know. This stuff is always messy.

> However, I do not have strong opinion here, so let me send v2.

Thanks.

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

      reply	other threads:[~2020-06-05  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04  6:32 Ladislav Michl
2020-06-05  8:41 ` Michael Olbrich
2020-06-05  9:27   ` Ladislav Michl
2020-06-05  9:53     ` Michael Olbrich [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=20200605095328.GA1716@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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