9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: 9front@9front.org
Subject: (upstream) curl on 9front
Date: Sat, 22 Aug 2020 06:52:07 +0200	[thread overview]
Message-ID: <20200822045207.kmjgnadv7ro5csdl@Hugin> (raw)

I am currently trying to go through all optional dependencies for netsurf to see
if I can put/update them in ports. I had an old curl port in there but it depended on
gawk and pulled in gnulib etc.

I was happy to see that Lufia had managed to get Plan9 (9legacy) support
upstream in curl some 5 months ago.

https://github.com/curl/curl/blob/master/plan9/README

as dependencies he wrote
- latest 9legacy patches
- zlib (OK)
- libressl


For the "latest 9legacy patches", he does not really specify which/what those may
be. Has most of 9legacy been integrated in 9front?

For libressl : I remember that an openssl port was replaced for the more native
libsec for python. I am not sure if that would be the best option here too. 
If I remember correctly, this move away from openssl also blocked later versions
of python so perhaps would it be interesting with a more up-to-date variant like
what Lufia is proposing?
https://github.com/libressl-portable/portable/pull/510

Looking at the different ssl options in curl, it looks like wolfssl might be an
attractive alternative with some openssl compat options.
https://curl.haxx.se/docs/ssl-compared.html



             reply	other threads:[~2020-08-22  4:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22  4:52 Jens Staal [this message]
2020-08-22  5:03 ` [9front] " ori
2020-08-23 19:36   ` Jens Staal

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=20200822045207.kmjgnadv7ro5csdl@Hugin \
    --to=staal1978@gmail.com \
    --cc=9front@9front.org \
    /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;
as well as URLs for NNTP newsgroup(s).