From: Eli Zaretskii <eliz@gnu.org>
To: YASUOKA Masahiko <yasuoka@yasuoka.net>
Cc: mattiase@acm.org, 42059@debbugs.gnu.org
Subject: bug#42059: 26.3; OpenBSD now has posix_openpt(3)
Date: Tue, 30 Jun 2020 17:32:01 +0300 [thread overview]
Message-ID: <83o8p0zkta.fsf@gnu.org> (raw)
In-Reply-To: <20200630.224929.476624940263769257.yasuoka@yasuoka.net> (message from YASUOKA Masahiko on Tue, 30 Jun 2020 22:49:29 +0900 (JST))
> Date: Tue, 30 Jun 2020 22:49:29 +0900 (JST)
> From: YASUOKA Masahiko <yasuoka@yasuoka.net>
> Cc: 42059@debbugs.gnu.org
>
> On Tue, 30 Jun 2020 13:52:21 +0200
> Mattias Engdegård <mattiase@acm.org> wrote:
> > Thanks for the patch! I'd be happy to apply it, but first: can you
> > confirm that older OpenBSD versions are still able to build Emacs with
> > that patch applied, or argue that this is a lesser problem?
>
> Although old versions might become not able to build Emacs with the
> patch, I suggest Emacs should have the patch.
>
> Firstly the versions are too old. posix_openpt(3) had been introduced
> to OpenBSD at OpenBSD 5.3, it was 7 years ago and 14 versions before
> the latest. It was 6 years ago when the last version which doesn't
> have posix_openpt(3) became out of support.
Would it be possible to contact the OpenBSD developers and/or the
persons who prepare the Emacs distros for OpenBSD, and ask for their
opinion about this? I mean, I wouldn't want to drop support for some
versions of an OS without at least consulting the relevant developers.
Thanks.
next prev parent reply other threads:[~2020-06-30 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 9:52 bug#42059: 26.3; OpenBSD now has posix_openpt(3) YASUOKA Masahiko
2020-06-27 3:56 ` YASUOKA Masahiko
2020-06-30 11:52 ` Mattias Engdegård
2020-06-30 13:49 ` YASUOKA Masahiko
2020-06-30 14:24 ` Mattias Engdegård
2020-06-30 15:36 ` Eli Zaretskii
2020-06-30 14:32 ` Eli Zaretskii [this message]
2020-07-01 11:23 ` Jeremie Courreges-Anglas
2020-07-01 14:24 ` Eli Zaretskii
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=83o8p0zkta.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42059@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=yasuoka@yasuoka.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.