From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libcurl: drop polarssl support
Date: Tue, 15 Apr 2014 13:22:08 -0300 [thread overview]
Message-ID: <534D5CB0.3040301@zacarias.com.ar> (raw)
In-Reply-To: <20140415181021.5ed849a7@skate>
On 04/15/2014 01:10 PM, Thomas Petazzoni wrote:
> It seems odd to drop a feature because we have a too old version of a
> dependency, no? Shouldn't we package polarssl 1.3, even if as a
> separate polarssl13 package?
The problem is that they aren't made to live together in a friendly way
and some packages don't take path arguments for it.
It would require quite some package patching since we'd need each
polarssl to live outside the default include/library PATHs.
We aren't dropping a feature itself, just a feature based on one of the
possible candidates that enables it, with gnutls, nss and openssl being
the other candidates for the job.
The big culprit here AFAIK is just openvpn, it's the only mofo that
won't do with polarssl 1.3. There are patches in the master branch
upstream for it, but that's to become openvpn 2.4 or so.
Maybe they're not hard to backport, i don't know, but it would require
more testing than just "it builds".
Or we can kill polarssl support in openvpn, not great either since the
other alternative is openssl.
Regards.
next prev parent reply other threads:[~2014-04-15 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 13:59 [Buildroot] [PATCH] libcurl: drop polarssl support Gustavo Zacarias
2014-04-15 16:10 ` Thomas Petazzoni
2014-04-15 16:22 ` Gustavo Zacarias [this message]
2014-04-15 16:31 ` Thomas Petazzoni
2014-04-15 17:18 ` Gustavo Zacarias
2014-04-15 19:55 ` Thomas Petazzoni
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=534D5CB0.3040301@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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