From: <mingli.yu@windriver.com>
To: <openembedded-devel@lists.openembedded.org>, <raj.khem@gmail.com>
Subject: [meta-oe][PATCH] cryptsetup: Upgrade to 2.1.0
Date: Thu, 14 Feb 2019 17:32:02 -0800 [thread overview]
Message-ID: <20190215013202.126333-1-mingli.yu@windriver.com> (raw)
From: Mingli Yu <mingli.yu@windriver.com>
Instead of hardcoding the version in SRC_URI,
get the version for the folder of the source
dynamically in SRC_URI.
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
---
.../cryptsetup/{cryptsetup_2.0.4.bb => cryptsetup_2.1.0.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta-oe/recipes-crypto/cryptsetup/{cryptsetup_2.0.4.bb => cryptsetup_2.1.0.bb} (83%)
diff --git a/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.0.4.bb b/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.1.0.bb
similarity index 83%
rename from meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.0.4.bb
rename to meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.1.0.bb
index cc7bc6e01..cf1d22242 100644
--- a/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.0.4.bb
+++ b/meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.1.0.bb
@@ -11,9 +11,9 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=32107dd283b1dfeb66c9b3e6be312326"
DEPENDS = "util-linux libdevmapper popt libgcrypt json-c"
-SRC_URI = "${KERNELORG_MIRROR}/linux/utils/${BPN}/v2.0/${BP}.tar.xz"
-SRC_URI[md5sum] = "ed42b31f67d05b05e392d1943d467b8d"
-SRC_URI[sha256sum] = "9d3a3c7033293e0c97f0ad0501fd5b4d4913ae497cbf70cca06633ccc54b5734"
+SRC_URI = "${KERNELORG_MIRROR}/linux/utils/${BPN}/v${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}/${BP}.tar.xz"
+SRC_URI[md5sum] = "41d8b985ef69242852b93e95d53e8e28"
+SRC_URI[sha256sum] = "a3eeb2741f8f3376d16585191f3c60e067dd987e096c3c4b073fab7748b1c897"
inherit autotools gettext pkgconfig
--
2.17.1
reply other threads:[~2019-02-15 1:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190215013202.126333-1-mingli.yu@windriver.com \
--to=mingli.yu@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.