From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] sqlite: rename to match upstream versioning
Date: Mon, 24 Feb 2014 19:03:13 +0200 [thread overview]
Message-ID: <1393261393-9602-2-git-send-email-sgw@linux.intel.com> (raw)
In-Reply-To: <1393261393-9602-1-git-send-email-sgw@linux.intel.com>
Since we are re-doing the version from a big number down to a dot
based number we have to bump the Package Epoch (PE).
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
.../sqlite/{sqlite3_3080301.bb => sqlite3_3.8.3.1.bb} | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
rename meta/recipes-support/sqlite/{sqlite3_3080301.bb => sqlite3_3.8.3.1.bb} (71%)
diff --git a/meta/recipes-support/sqlite/sqlite3_3080301.bb b/meta/recipes-support/sqlite/sqlite3_3.8.3.1.bb
similarity index 71%
rename from meta/recipes-support/sqlite/sqlite3_3080301.bb
rename to meta/recipes-support/sqlite/sqlite3_3.8.3.1.bb
index 8ed01a9..ca3a05c 100644
--- a/meta/recipes-support/sqlite/sqlite3_3080301.bb
+++ b/meta/recipes-support/sqlite/sqlite3_3.8.3.1.bb
@@ -2,12 +2,14 @@ require sqlite3.inc
LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=65f0a57ca6928710b418c094b3570bb0"
-SRC_URI = "http://www.sqlite.org/2014/sqlite-autoconf-${PV}.tar.gz"
+PE = "1"
+SQLITE_PV = "3080301"
+SRC_URI = "http://www.sqlite.org/2014/sqlite-autoconf-${SQLITE_PV}.tar.gz"
SRC_URI[md5sum] = "509ff98d8dc9729b618b7e96612079c6"
SRC_URI[sha256sum] = "de5dc216e9289fabf027f78dbbface32ffc8c6341b7d841d0814b1a452ffdb8c"
-S = "${WORKDIR}/sqlite-autoconf-${PV}"
+S = "${WORKDIR}/sqlite-autoconf-${SQLITE_PV}"
# Provide column meta-data API
BUILD_CFLAGS += "-DSQLITE_ENABLE_COLUMN_METADATA"
--
1.8.3.1
next prev parent reply other threads:[~2014-02-24 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 17:03 [PATCH 1/2] sqlite3: Update to 3080301 Saul Wold
2014-02-24 17:03 ` Saul Wold [this message]
2014-02-24 17:23 ` [PATCH 2/2] sqlite: rename to match upstream versioning Paul Eggleton
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=1393261393-9602-2-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.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