Upstream SQLite3 provides an `sqlite3_rsync` tool which is useful for creating backups/synchronized copies of SQLite databases. This can be built with `make sqlite3_rsync`. Here is an example patch: ``` --- ./sqlite-3.49.2.ebuild 2025-05-29 21:05:08.335953950 -0700 +++ ./sqlite-3.49.2-r1.ebuild 2025-05-29 21:23:31.333918186 -0700 @@ -338,7 +338,7 @@ emake HAVE_TCL="$(usev tcl 1)" TCLLIBDIR="${EPREFIX}/usr/$(get_libdir)/${P}" if use tools && multilib_is_native_abi; then - emake changeset dbdump dbhash dbtotxt index_usage rbu scrub showdb showjournal showshm showstat4 showwal sqldiff sqlite3_analyzer sqlite3_checker sqlite3_expert sqltclsh + emake changeset dbdump dbhash dbtotxt index_usage rbu scrub showdb showjournal showshm showstat4 showwal sqldiff sqlite3_analyzer sqlite3_checker sqlite3_expert sqlite3_rsync sqltclsh fi if [[ ${PV} == 9999 ]] && use doc && multilib_is_native_abi; then @@ -411,6 +411,7 @@ install_tool sqlite3_analyzer sqlite3-analyzer install_tool sqlite3_checker sqlite3-checker install_tool sqlite3_expert sqlite3-expert + install_tool sqlite3_rsync sqlite3-rsync install_tool sqltclsh sqlite3-tclsh unset -f install_tool ``` One note: when the source or destination is on a remote host, `sqlite3_rsync` invokes `sqlite3_rsync` on the remote end via SSH. It seems like for other tools, the ebuild conventionally renames `sqlite_*` to `sqlite-*` (i.e., replaces an underscore with a hyphen), which would then require the user of `sqlite3_rsync` to specify `--exe sqlite3-rsync` if the convention is followed for this tool as well. This is workable, but inconvenient and does not match the behavior of other distributions which package the `sqlite3_*` tools under their original names. I'm not familiar with the context of Gentoo's decision here. Reproducible: Always Steps to Reproduce: Build sqlite3 with USE=tools Actual Results: sqlite3_rsync is not installed Expected Results: sqlite3_rsync is installed
