All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openvpn: add option to use mbed TLS instead of OpenSSL
Date: Mon, 18 May 2020 07:15:08 +0200	[thread overview]
Message-ID: <20200518071508.5c8f134c@windsurf.home> (raw)
In-Reply-To: <CACm0Nn2ZFPuHKQoCh5pdakeHh80q-4nzt1umH0A5Rbon_ktgZw@mail.gmail.com>

Hello Ed,

On Mon, 18 May 2020 04:45:35 +0300
Ed Spiridonov <edo.rus@gmail.com> wrote:

> In the case proposed by you, OpenSSL is selected automagically without
> ability to unselect (until mbed?TLS is selected manually).
> How can the user find out that mbed?TLS could be used instead of OpenSSL?
> Press help on OpenVPN item? Kconfig shows dependencies here, but not a
> condition (if !BR2_PACKAGE_MBEDTLS).
> Look into package/openvpn/Config.in?
> Of course, detailed explanation could be added into OpenVPN help. But
> nobody reads help for *all* selected items.

All what you're saying here is valid for a huge number of packages
where Buildroot automatically makes use of optional dependencies if
they are available.

For example:

ifeq ($(BR2_PACKAGE_XLIB_LIBXRANDR),y)
LIBGTK3_CONF_OPTS += --enable-xrandr
LIBGTK3_DEPENDENCIES += xlib_libXrandr
else
LIBGTK3_CONF_OPTS += --disable-xrandr
endif

libgtk3 will automatically have xrandr support when
BR2_PACKAGE_XLIB_LIBXRANDR is enabled. The user has no way to "know"
about it, except by reading libgtk3.mk.

But this allows to limit the number of Config.in options we have. We
already have thousands of them, and if we were to add such options for
each optional dependency of all packages, we would have tens of
thousands of Config.in options.

There are however some packages where we add explicit sub-options, for
various reasons, but that is not the general case.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-05-18  5:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 22:31 [Buildroot] [PATCH] package/openvpn: add option to use mbed TLS instead of OpenSSL Ed Spiridonov
2020-05-15 17:30 ` Ed Spiridonov
2020-05-15 19:17   ` Heiko Thiery
2020-07-26 12:01     ` Ed Spiridonov
2020-05-15 20:10 ` Thomas Petazzoni
2020-05-15 20:39   ` Ed Spiridonov
2020-05-15 20:47     ` Thomas Petazzoni
     [not found]       ` <CACm0Nn0WyTPDnSyA+7bj10GddAstx0YkyUAuERcRSLSf0CyzRA@mail.gmail.com>
2020-05-15 21:18         ` Thomas Petazzoni
2020-05-18  1:45   ` Ed Spiridonov
2020-05-18  5:15     ` Thomas Petazzoni [this message]
2020-05-23 18:38       ` Ed Spiridonov
2020-07-10 18:39       ` Ed Spiridonov
2020-10-10  6:43         ` Ed Spiridonov

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=20200518071508.5c8f134c@windsurf.home \
    --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.