public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] sqlite: Update to version 3480000
Date: Fri, 17 Jan 2025 12:26:10 +0100	[thread overview]
Message-ID: <20250117112612.3250389-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250117112612.3250389-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3846 bytes --]

- Update from version 3470200 to 3480000
- Update of rootfile not required
- Changelog
    3480000
	Refactor the "configure" script used to help build SQLite from canonical
	 sources, to fix bugs, improve performance, and make the code more maintainable.
	    This does not affect the "configure" script in the
	     sqlite3-autoconf-NNNNNNN.tar.gz "amalgamation tarball", only the canonical
	     sources. The build system for the amalgamation tarball is unchanged. If
	     you are using the amalgamation tarball, nothing about this change log
	     entry applies to you.
	    The key innovation here is that Autosetup is now used instead of GNU
	     Autoconf. That seems like a big change, but it is really just an
	     implementation detail. The ./configure script is coded very differently,
	     but should work the same as before.
	    One advantage of the new configure is that you no longer need to install
	     TCL in order to build most SQLite targets. TCL is still required to run
	     tests or to build accessory programs (like sqlite3_analyzer) that use TCL,
	     but it is not required for most common targets. Hence, as of this release,
	     the only build dependencies are a C compiler and "make" or "nmake".
	Improved EXPLAIN QUERY PLAN output for covering indexes.
	Allow a two-argument version of the iif() SQL function. Also allow if() as an
	 alternative spelling for iif().
	Add the ".dbtotxt" command to the CLI.
	Add the SQLITE_IOCAP_SUBPAGE_READ property to the xDeviceCharacteristics method
	 of the sqlite3_io_methods object.
	Add the SQLITE_PREPARE_DONT_LOG option to sqlite3_prepare_v3() that prevents
	 warning messages being sent to the error log if the SQL is ill-formed. This
	 allows sqlite3_prepare_v3() to be used to do test compiles of SQL to check for
	 validity without polluting the error log with false messages.
	Increase the minimum allowed value of SQLITE_LIMIT_LENGTH from 1 to 30.
	Added the SQLITE_FCNTL_NULL_IO file control.
	Extend the FTS5 auxiliary API xInstToken() to work with prefix queries via the
	 insttoken configuration option and the fts5_insttoken() SQL function.
	Increase the maximum number of arguments to an SQL function from 127 to 1000.
	Remove vestigial traces of SQLITE_USER_AUTHENTICATION.
	Various obscure bug fixes.

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/sqlite | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/sqlite b/lfs/sqlite
index ee7d96033..3f7274a5e 100644
--- a/lfs/sqlite
+++ b/lfs/sqlite
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2024  IPFire Team  <info(a)ipfire.org>                     #
+# Copyright (C) 2007-2025  IPFire Team  <info(a)ipfire.org>                     #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 3470200
+VER        = 3480000
 
 THISAPP    = sqlite-autoconf-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 3c2ea6cba87f5850a9c2355cc213182d351a9d7b26687f77c07178526b300eec19040804a713e6fa3db704dcb4e0e4921ef849f6bc14496adcfc22875048c640
+$(DL_FILE)_BLAKE2 = 9bfa33875ddb964efef7c91546be0819597a697e05789fb18c6b7e41d870d838c5446a99a64ec57c564f3d995fd7893fb7617c4d0399dd0924b8a3c5986f5698
 
 install : $(TARGET)
 
-- 
2.48.1


  reply	other threads:[~2025-01-17 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 11:26 [PATCH] haproxy: Update to version 3.1.2 Adolf Belka
2025-01-17 11:26 ` Adolf Belka [this message]
2025-01-17 11:26 ` [PATCH] tmux: Update to version 3.5a Adolf Belka
2025-01-17 11:26 ` [PATCH] tzdata: Update to version 2025a Adolf Belka

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=20250117112612.3250389-2-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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