From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] LibreSSL support?
Date: Mon, 5 Dec 2016 23:33:00 +0100 [thread overview]
Message-ID: <20161205223300.GA5002@itchy> (raw)
Hi all!
Are there any plans for adding support for LibreSSL?
I've found a patch [1] in patchwork, from M. Hadjinlian, posted two
years ago. The review concludes with the need for the introduction of a
virtual package, as LibreSSL uses the same names for its binaries and
libraries as OpenSSL (openssl, libcrypto, libssl and libtls).
So, what would be the best solution:
a)
1. introduce the virtual package openssl-compat.
2. make libressl and openssl provide openssl-compat.
3. update all packages depending on/selecting openssl to depend on/select
openssl-compat.
b)
1. rename openssl to openssl-genuine.
2. introduce virtual package openssl.
3. make openssl-genuine and libressl provide openssl.
Comments and suggestions welcome.
[1] https://patchwork.ozlabs.org/patch/398963/
--
ELB
next reply other threads:[~2016-12-05 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 22:33 Eric Le Bihan [this message]
2016-12-05 22:36 ` [Buildroot] LibreSSL support? Maxime Hadjinlian
2016-12-06 22:26 ` Eric Le Bihan
2016-12-06 23:46 ` Arnout Vandecappelle
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=20161205223300.GA5002@itchy \
--to=eric.le.bihan.dev@free.fr \
--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