Log message:
databases/sqlite3: Fix cross-build.

Conditional on USE_CROSS_COMPILE = yes, so no change to native build.
Didn't cross-build without this, so no need for revbump.

Log message:
sqlite3: Remove jimtcl dependency.

The sqlite3 autoconf distribution includes a bundled jimsh0 that is used to
bootstrap in the case of the host not providing a TCL implementation.  Simply
use that rather than depending on jimtcl, which is non-portable.

Fixes build on at least Solaris/illumos.  Tested on SmartOS, macOS, and NetBSD,
with macOS being of particular interest as it ships a native implementation of
tclsh so does not use the bootstrap version.

While here perform pkglint cleanup.  Bump PKGREVISION.

Log message:
databases/sqlite3: Temporarily disable zlib for now.

Since the update, pkg_add sqlite3 is newly broken on some platforms.
See comment for details.

Log message:
sqlite3: updated to 3.49.1

Prior changes from version 3.49.0 (2025-02-06):

Enhancements to the query planner:
Improve the query-time index optimization so that it works on WITHOUT ROWID tables.
Better query plans for large star-query joins. This fixes three different \ 
performance regressions that were reported on the SQLite Forum.
When two or more queries have the same estimated cost, use the one with the \ 
fewer bytes per row.
Enhance the iif() SQL function so that it can accept any number of arguments \ 
greater than or equal to two.
Enhance the session extension so that it works on databases that make use of \ 
generated columns.
Omit the SQLITE_USE_STDIO_FOR_CONSOLE compile-time option which was not \ 
implemented correctly and never worked right. In its place add the \ 
SQLITE_USE_W32_FOR_CONSOLE_IO compile-time option. This option applies to \ 
command-line tools like the CLI only, not to the SQLite core. It causes Win32 \ 
APIs to be used for console I/O instead of stdio. This option affects Windows \ 
builds only.
Three new options to sqlite3_db_config(). All default to "on".
SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE
SQLITE_DBCONFIG_ENABLE_ATTACH_WRITE
SQLITE_DBCONFIG_ENABLE_COMMENTS
Replace Autotools with Autosetup for the configure script used in the \ 
precompiled amalgamation tarball. The configure script for the canonical source \ 
code was changed to Autosetup in the previous (3.48.0) release. Only the main \ 
SQLite configure script in the amalgamation tarball is changed. The (deprecated) \ 
configuration script use by TEA subdirectory of the amalgamation tarball still \ 
relies on Autotools.
Various minor patches and fixes for problems seen in the 3.48.0 release.

Changes in this specific patch release, version 3.49.1 (2025-02-18):

Improve portability of makefiles and configure scripts.
Fix a bug in the concat_ws() function, introduced in version 3.44.0, that could \ 
lead to a memory error if the separator string is very large (hundreds of \ 
megabytes).
Enhanced the SQLITE_DBCONFIG_LOOKASIDE interface to make it more robust against \ 
misuse.

Log message:
databases/sqlite3: fix outdated configure option name

Log message:
sqlite3: updated to 3.48.0

SQLite Release 3.48.0 On 2025-01-14

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.

Log message:
databases/sqlite3: Spruce up build options.

1. Document reasoning for each of the build-time options available and
   set a rubric for which ones to enable in future updates.

2. Enable some options that look well-justified.  I went through all
   the options at https://www.sqlite.org/compile.html, applied the
   rubric, and compared to several other general-purpose packaging
   systems.

(Happy to discuss and amend the rubric and the choice of options --
this should be viewed as a starting point for review, testing, and
tweaking, not an inviolably final decision.)

3. Nix PKG_OPTIONS that are default-on upstream -- these haven't done
   anything in a while.  If you want to add these back, then:

   (a) they should be in PKG_SUGGESTED_OPTIONS (because they're
       already enabled by default upstream), and

   (b) you'll have to set and test the appropriate SQLITE_OMIT_*
       option.

   Options removed:
   - deserialize (default-on upstream anyway)
   - fts (default-on upstream anyway)
   - sqlite3-dbstat (unconditionally enabled in pkgsrc now because
     needed by downstream packages)

   Options remaining:
   - icu

4. Nix some deprecated options like SQLITE_ENABLE_LOAD_EXTENSION.

Additions to CONFIGURE_ARGS:
--enable-fts3 (paranoia, default-on upstream anyway)
--enable-fts4 (paranoia, default-on upstream anyway)
--enable-fts5 (paranoia, default-on upstream anyway)
--enable-math (paranoia, default-on upstream anyway)
--enable-rtree (paranoia, default-on upstream anyway)
--enable-session

Removals from CONFIGURE_ARGS: none

Additions to CFLAGS:
-DSQLITE_ENABLE_DBSTAT_VTAB
-DSQLITE_ENABLE_FTS3_PARENTHESIS
-DSQLITE_ENABLE_HIDDEN_COLUMNS
-DSQLITE_ENABLE_STMTVTAB

Removals from CFLAGS:
-DSQLITE_ENABLE_LOAD_EXTENISON (default-on upstream now; need
  SQLITE_OMIT_LOAD_EXTENSION to reverse)
-DSQLITE_ENABLE_MATH_FUNCTIONS (replaced by --enable-math for better
  build-time error checking)

PR pkg/58448: databases/sqlite3 is missing dbstat option

Log message:
sqlite3: updated to 3.47.2

version 3.47.2 (2024-12-07):

Fix a problem in text-to-floating-point conversion for SQLite that can cause \ 
values between '1.8446744073709550592eNNN' and '1.8446744073709551609eNNN' for \ 
any exponent NNN to be rendered incorrectly. In other words, some numeric text \ 
values where the first 16 significant digits are '1844674407370955' might be \ 
converted into the wrong floating-point value. See forum thread \ 
569a7209179a7f5e. This problem only arises on x64 and i386 hardware. The problem \ 
was introduced in 3.47.0.
Other minor bug fixes.