[PATCH] update configure.ac to follow new download location sqlite amalgamation

[Lieven Govaerts <sv...@mobsol.be>]

Hi,


seems like the sqlite developers have changed the naming conventions
for the sqlite amalgamation distribution package + stopped creating
the .tar.gz file.

The new address is now:
http://www.sqlite.org/sqlite-amalgamation-3071300.zip

instead of:
http://www.sqlite.org/sqlite-amalgamation-3.7.12.tar.gz

Attached patch updates configure to this new location. I can commit
this myself, but I'm wondering if I'm not overlooking something
obvious since this seems to be a strange move from the sqlite devs
side.


[[
Sqlite amalgamation distributions are now distributed as .zip and with a new
naming convention.

* configure.ac: update url of sqlite amalgamation file to its current location.
]]

Lieven

Re: [PATCH] update configure.ac to follow new download location sqlite amalgamation

[Ben Reser <be...@reser.org>]

On Sat, Aug 11, 2012 at 2:15 AM, Lieven Govaerts <sv...@mobsol.be> wrote:
> Attached patch updates configure to this new location. I can commit
> this myself, but I'm wondering if I'm not overlooking something
> obvious since this seems to be a strange move from the sqlite devs
> side.

+1

Looks to me like they've redone how they're doing releases.  This page
no longer has a sha1sum for the lastest releases sqlite.c file:
http://www.sqlite.org/draft/changes.html

I've downloaded the new file and checked the sha1sum of sqlite.c
against the one listed on that page.

Re: [PATCH] update configure.ac to follow new download location sqlite amalgamation

[Daniel Shahaf <d....@daniel.shahaf.name>]

Lieven Govaerts wrote on Sat, Aug 11, 2012 at 11:15:16 +0200:
> Hi,
> 
> 
> seems like the sqlite developers have changed the naming conventions
> for the sqlite amalgamation distribution package + stopped creating
> the .tar.gz file.
> 
> The new address is now:
> http://www.sqlite.org/sqlite-amalgamation-3071300.zip
> 
> instead of:
> http://www.sqlite.org/sqlite-amalgamation-3.7.12.tar.gz
> 
> Attached patch updates configure to this new location. I can commit
> this myself, but I'm wondering if I'm not overlooking something
> obvious since this seems to be a strange move from the sqlite devs
> side.

FWIW, I recall someone (Arfrever?) patching get-deps.sh in the past to
account for change in the upstream URL / naming scheme of sqlite.