From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] LibreSSL, introduce virtual/openssl
Date: Fri, 23 Jan 2015 09:05:58 +0000 [thread overview]
Message-ID: <CAHcsgXSAdjGm+D-8UbkXNMKrftf=PR=3X24P6eKT+zL=+3fG4g@mail.gmail.com> (raw)
In-Reply-To: <20150123065607.74cd64d1@pomiot.lan>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
But they don't. See my two blog posts on the matter. ABI compatibility is
explicitly not. What they care about.
On 23 Jan 2015 05:56, "Michał Górny" <mgorny@gentoo.org> wrote:
> Dnia 2015-01-23, o godz. 01:51:24
> hasufell <hasufell@gentoo.org> napisał(a):
>
> > Regarding the last libav discussion I think we should also go with a
> > "libressl" USE flag instead of creating a virtual that makes handling
> > SUBSLOTs impossible.
>
> If libressl and openssl would have matching ABIs, that wouldn't be
> necessary and you could what virtual/libudev does, i.e. explicit
> subslot deps.
>
> --
> Best regards,
> Michał Górny
>
[-- Attachment #2: Type: text/html, Size: 991 bytes --]
next prev parent reply other threads:[~2015-01-23 9:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 12:37 [gentoo-dev] [RFC] LibreSSL, introduce virtual/openssl hasufell
2014-07-12 14:28 ` Anthony G. Basile
2014-07-12 14:35 ` hasufell
2014-07-12 15:42 ` William Hubbs
2014-07-12 18:51 ` Dirkjan Ochtman
2014-07-13 17:59 ` hasufell
2014-07-15 14:18 ` Matthew Summers
2014-07-15 14:47 ` hasufell
2014-07-16 7:16 ` [gentoo-dev] " Duncan
2015-01-23 1:51 ` [gentoo-dev] " hasufell
2015-01-23 5:56 ` Michał Górny
2015-01-23 9:05 ` Diego Elio Pettenò [this message]
2015-01-23 13:25 ` Anthony G. Basile
2015-01-23 20:18 ` hasufell
2015-01-23 22:37 ` Rich Freeman
2015-01-26 10:43 ` Peter Stuge
2015-01-26 12:08 ` Rich Freeman
2015-01-26 16:01 ` Peter Stuge
2015-01-26 17:55 ` Rich Freeman
2015-01-27 0:54 ` hasufell
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='CAHcsgXSAdjGm+D-8UbkXNMKrftf=PR=3X24P6eKT+zL=+3fG4g@mail.gmail.com' \
--to=flameeyes@flameeyes.eu \
--cc=gentoo-dev@lists.gentoo.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