On Thu, Oct 25, 2012 at 12:42 AM, Darren Duncan <dar...@darrenduncan.net>wrote:
> Kees Nuyt wrote: > >> On Thu, 25 Oct 2012 00:12:16 +0200, Baruch Burstein >> <bmburst...@gmail.com> wrote: >> >> Is there a permanent link I can use that will always point to the latest >>> amalgamation (or .zip containing it)? I would like to automate a make >>> script that will use the latest sqlite. >>> I know I can use a link to the latest release in the repo, but that >>> means I >>> would need to build the amalgamation as part of this make step. >>> >> >> You make it sound very difficult to build the amalgamation source, >> but actually it's just "make sqlite3.c". >> >> So the easiest way really is to: >> * clone the fossil repo (once), >> * pull in updates periodically, >> * ./configure with the proper options/defines/omits >> for whatever your project needs, >> * make sqlite3.c, * make your project. >> > > I don't think that answer is appropriate for some common use cases, which > may include the original requestor. Say for example and end user of the > DBD::SQLite Perl module that wants to pull in the latest SQLite version to > build it against, without having to specify a version. We shouldn't expect > such a user to have a fossil client, they should just be able to pull the > amalgamation tarball over the web. -- Darren Duncan > I don't remember the exact path offhand, but fossil web ui has a URL that return the requested checkin as a tarball, no need for a fossil client. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
