From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>,
buildroot@buildroot.org,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/python3: drop libressl support
Date: Wed, 27 Apr 2022 10:31:02 +0200 [thread overview]
Message-ID: <20220427103102.7f934c1f@windsurf> (raw)
In-Reply-To: <20220427035039.1664864-1-james.hilliard1@gmail.com>
Hello James,
On Tue, 26 Apr 2022 21:50:39 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> Libressl is no longer supported as of python 3.10.
>
> See: https://peps.python.org/pep-0644/#libressl
>
> Fixes:
> - http://autobuild.buildroot.net/results/a16/a160cfdc9dfc036c4dc41af1c796f8838d91c573
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Thanks for your patch. I think it raises one question: is libressl
still relevant? Should we still support it?
My understanding was that it is not really a successful fork, and in
the end, openssl has mostly caught up and remains the de-facto standard
implementation. See https://lwn.net/Articles/841664/.
I don't have a very well-informed opinion, but perhaps we should think
about this?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-04-27 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 3:50 [Buildroot] [PATCH 1/1] package/python3: drop libressl support James Hilliard
2022-04-27 8:31 ` Thomas Petazzoni via buildroot [this message]
2022-04-27 8:42 ` James Hilliard
2022-04-27 15:41 ` Arnout Vandecappelle
2022-04-27 20:09 ` Peter Korsgaard
2022-04-29 9:53 ` Arnout Vandecappelle
2022-04-27 19:38 ` Arnout Vandecappelle
2022-05-27 9:33 ` Peter Korsgaard
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=20220427103102.7f934c1f@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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