Skip to contentSkip to conversation

sqlite: use new upstream file versioning convention

PATCH New Gustavo Zacarias 2 participants 2 messages Dec 27, 2010

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 sqlite: use new upstream file versioning convention

Upstream decided to change the file naming convention.

sqlite-amalgamation is now sqlite-autoconf

For a given version, say, 3.7.4 (W.X.Y) upstream now uses WXXYYZZ with Z reserved for minor fix versions, all zero padded.
Thus 3.7.4 is 3070400, 3.7.4.1 would be 3070401.

---
 package/sqlite/sqlite.mk |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
package/sqlite/sqlite.mk +2 -2
index 8b0e13e..7b3a983 100644
@@ -4,8 +4,8 @@
 #
 #############################################################
 
-SQLITE_VERSION = 3.7.4
-SQLITE_SOURCE = sqlite-amalgamation-$(SQLITE_VERSION).tar.gz
+SQLITE_VERSION = 3070400
+SQLITE_SOURCE = sqlite-autoconf-$(SQLITE_VERSION).tar.gz
 SQLITE_SITE = http://www.sqlite.org
 SQLITE_INSTALL_STAGING = YES
 
Signature · 1 line
1.7.2.2
#1 lore raw

PATCH 1/1 sqlite: use new upstream file versioning convention

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Gustavo" == Gustavo Zacarias <[email protected]> writes:

Gustavo> Upstream decided to change the file naming convention. Gustavo> sqlite-amalgamation is now sqlite-autoconf

Committed, thanks.

Signature · 1 line
Bye, Peter Korsgaard