Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Update bind to lates ESV version 9.16
Date: Thu, 27 Feb 2020 12:56:06 -0800	[thread overview]
Message-ID: <20200227205608.26788-1-akuster808@gmail.com> (raw)

Please consider this last minute addition to 3.1.

Bind 9.16.0 just dropped and is the latest ESV. It requires libuv from meta-oe so 
please it should be added to core too.

The current 9.11 ESV is planned to be EOL'd in the middle 3.1 LTS release.

Armin Kuster (2):
  libuv: needed by bind 9.16
  bind: Update to latest ESV version 9.16

 ....in-remove-useless-L-use_openssl-lib.patch | 30 --------------
 ...d-V-and-start-log-hide-build-options.patch | 33 +++++++--------
 ...ching-for-json-headers-searches-sysr.patch | 14 +++----
 .../bind/{bind_9.11.13.bb => bind_9.16.0.bb}  | 40 +++++++------------
 .../libuv/libuv_1.34.0.bb                     | 19 +++++++++
 5 files changed, 57 insertions(+), 79 deletions(-)
 delete mode 100644 meta/recipes-connectivity/bind/bind/0001-configure.in-remove-useless-L-use_openssl-lib.patch
 rename meta/recipes-connectivity/bind/{bind_9.11.13.bb => bind_9.16.0.bb} (77%)
 create mode 100644 meta/recipes-connectivity/libuv/libuv_1.34.0.bb

-- 
2.17.1



             reply	other threads:[~2020-02-27 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 20:56 Armin Kuster [this message]
2020-02-27 20:56 ` [PATCH 1/2] libuv: needed by bind 9.16 Armin Kuster
2020-02-27 22:33   ` Anuj Mittal
2020-02-27 22:43     ` akuster808
2020-02-27 20:56 ` [PATCH 2/2] bind: Update to latest ESV version 9.16 Armin Kuster
2020-03-03 23:28   ` Richard Purdie
2020-05-31 16:27   ` [OE-core] " Alexander Kanavin

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=20200227205608.26788-1-akuster808@gmail.com \
    --to=akuster808@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