From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4, 1/1] package/uacme: don't allow mbedtls with ualpn
Date: Mon, 27 Apr 2020 21:31:28 +0200 [thread overview]
Message-ID: <20200427213128.70d9e95f@windsurf.home> (raw)
In-Reply-To: <20200426192130.GD28666@scaer>
On Sun, 26 Apr 2020 21:21:30 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > > Sorry, but this is still not correct: enable mbedtls, then enable uacme
> > > and ualpn: there is no crypto backend selectable in the choice...
> > Do we need a choice in the first place ?
>
> We already have a few packages (libcurl, libssh, libssh2) that have a
> choice for the crypto backend, so why not for uacme?
Are they really needed? Don't we generally try to use automatic
dependencies when possible?
We also have plenty of packages without any choice, for example:
ifeq ($(BR2_PACKAGE_GNUTLS),y)
LIBNICE_CONF_OPTS += --with-crypto-library=gnutls
LIBNICE_DEPENDENCIES += gnutls
else
LIBNICE_CONF_OPTS += \
--with-crypto-library=openssl \
--with-openssl=$(STAGING_DIR)/usr
LIBNICE_DEPENDENCIES += openssl
endif
ifeq ($(BR2_PACKAGE_GNUTLS),y)
MSMTP_CONF_OPTS += --with-tls=gnutls
MSMTP_DEPENDENCIES += gnutls
else ifeq ($(BR2_PACKAGE_OPENSSL),y)
MSMTP_CONF_OPTS += --with-tls=openssl
MSMTP_DEPENDENCIES += openssl
else
MSMTP_CONF_OPTS += --with-tls=no
endif
etc, etc.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-04-27 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 11:05 [Buildroot] [PATCH v4, 1/1] package/uacme: don't allow mbedtls with ualpn Fabrice Fontaine
2020-04-26 11:36 ` Yann E. MORIN
2020-04-26 12:13 ` Thomas Petazzoni
2020-04-26 12:30 ` Fabrice Fontaine
2020-04-26 16:07 ` Nicola Di Lieto
2020-04-26 19:38 ` Yann E. MORIN
2020-04-26 19:21 ` Yann E. MORIN
2020-04-27 19:31 ` 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=20200427213128.70d9e95f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox