From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libsoup: update to version 2.32.2 and enable SSL support
Date: Wed, 13 Jul 2011 21:02:51 +0200 [thread overview]
Message-ID: <1310583771.11691.2.camel@bender> (raw)
In-Reply-To: <20110713191252.4e0c7a65@skate>
On Wed, 2011-07-13 at 19:12 +0200, Thomas Petazzoni wrote:
> Le Wed, 13 Jul 2011 18:58:43 +0200,
> Sven Neumann <s.neumann@raumfeld.com> a ?crit :
>
> > +ifeq ($(BR2_PACKAGE_GNUTLS),y)
> > +LIBSOUP_DEPENDENCIES += gnutls
> > +LIBSOUP_CONF_OPT += --enable-ssl
> > +else
> > +LIBSOUP_CONF_OPT += --disable-ssl
> > +endif
> > +
>
> Question not specific to your patch: how are we going to handle openssl
> vs. gnutls in Buildroot? Is gnutls a drop-in replacement for openssl?
> It'd be a mess to have a portion of our packages using openssl for SSL,
> and another portion of our packages using gnutls for SSL, no?
Honestly, this mess seems hard to avoid. We are using openssl for ssh
and also in our own software stack. And we also need libsoup with
support for HTTPS. And it seems the only way to get that is to depend on
gnutls.
Sven
prev parent reply other threads:[~2011-07-13 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 16:58 [Buildroot] [PATCH 1/2] libsoup: update to version 2.32.2 and enable SSL support Sven Neumann
2011-07-13 16:58 ` [Buildroot] [PATCH 2/2] libsoup: explicitly pass gcrypt prefix to the configure script Sven Neumann
2011-07-13 17:12 ` [Buildroot] [PATCH 1/2] libsoup: update to version 2.32.2 and enable SSL support Thomas Petazzoni
2011-07-13 19:02 ` Sven Neumann [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=1310583771.11691.2.camel@bender \
--to=s.neumann@raumfeld.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