From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH 1/5] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version
Date: Tue, 10 Apr 2018 15:39:06 +0300 [thread overview]
Message-ID: <a9c4058e-e33b-8c31-6cd7-915dcaa11437@linux.intel.com> (raw)
In-Reply-To: <20180410124338.GA1343@jama>
On 04/10/2018 03:43 PM, Martin Jansa wrote:
> On Tue, Apr 10, 2018 at 03:07:43PM +0300, Alexander Kanavin wrote:
>> Openssl 1.0 can still be utilized by depending on 'openssl10' recipe.
>
> Does this really work now?
>
> I think it will fail again when both openssl versions end up in RSS.
The only known case where this happened was Qt5 (because it also wanted
python), and Qt5 gained openssl 1.1 support in the latest released version.
Alex
prev parent reply other threads:[~2018-04-10 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 12:07 [RFC][PATCH 1/5] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version Alexander Kanavin
2018-04-10 12:07 ` [RFC][PATCH 2/5] cryptodev-tests: port to openssl 1.1 Alexander Kanavin
2018-04-10 12:07 ` [RFC][PATCH 3/5] openssl: update to 1.1.1 Alexander Kanavin
2018-04-10 21:20 ` Andre McCurdy
2018-04-11 10:09 ` Alexander Kanavin
2018-04-11 18:56 ` Andre McCurdy
2018-04-10 12:07 ` [RFC][PATCH 4/5] libressl: add a recipe to support openssh Alexander Kanavin
2018-04-11 8:38 ` Andre McCurdy
2018-04-11 10:03 ` Alexander Kanavin
2018-04-11 19:07 ` Andre McCurdy
2018-04-10 12:07 ` [RFC][PATCH 5/5] openssh: update to 7.7p1 and depend on libressl Alexander Kanavin
2018-04-10 12:34 ` ✗ patchtest: failure for "[RFC] openssl: rename openssl ..." and 4 more Patchwork
2018-04-10 12:43 ` [RFC][PATCH 1/5] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version Martin Jansa
2018-04-10 12:39 ` Alexander Kanavin [this message]
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=a9c4058e-e33b-8c31-6cd7-915dcaa11437@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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