From: Jens Staal <staal1978@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [Patch] APE changes (2019 Lufia patches)
Date: Mon, 22 Feb 2021 06:20:21 +0100 [thread overview]
Message-ID: <20210222052021.sfasmyxvyq3w7fi7@Krypton> (raw)
In-Reply-To: <BEB40102F9FDE534A0B9DDF6CC190312@eigenstate.org>
On Sun, Feb 21, 2021 at 08:14:40PM -0800, ori@eigenstate.org wrote:
> Quoth bsdsm@sdf.org:
> > Hello,
> >
> > This patch is a pared down version of the changes that Lufia made back in
> > 2019; the essential changes from 'add funcs and types to APE' and all of
> > 'add #include_next directive'. An unmodified diff of the former pull
> > request can be found here[1] for comparison.
> >
> > This has only been tested on an amd64 build. Works cleanly with tree as of
> > Feb 20, 2021 changes.
>
> Thanks for taking the time to port it over. Are there any
> programs in particular that you wanted this for/that use
> the APIs exposed?
>
wow great! Looking through the patch, it seems to contain a lot of
things that I have been missing before (I do not remember them all, but
for a lot of them I resorted to ugly gnulib hacks). Lufia also got
upstream support for curl. I am not sure, but I think that that upstream
curl support depends on these patches (and a port of libressl that lufia
also made).
One question: The definition of SIGWINCH in pyconfig.h. Considering that
Python (hopefully) will be depreceated in the default 9front when it is
moved from hg to git9, would it not be better to have this at signal.h?
When real life is getting a bit less chaotic I hope to revisit porting
nethack on pdcursesmod (where we now have upstream/official support).
Some of the things here might help there (I don't remember at the
moment).
next prev parent reply other threads:[~2021-02-22 5:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 2:48 bsdsm
2021-02-22 4:14 ` ori
2021-02-22 5:20 ` Jens Staal [this message]
2021-02-25 2:15 ` ori
2021-02-25 2:21 ` ori
2021-02-25 16:37 ` Aaron
2021-02-25 18:06 ` ori
2021-02-26 10:28 ` cinap_lenrek
2021-02-26 15:38 ` Lucas Francesco
2021-02-26 19:23 ` [9front] " bsdsm
2021-03-01 3:41 ` ori
2021-03-15 3:20 ` ori
2021-03-15 3:36 ` ori
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=20210222052021.sfasmyxvyq3w7fi7@Krypton \
--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).