appreciate that with tooling changes this might be more complicated than normal - https://sqlite.org/releaselog/3_49_1.html - https://msteveb.github.io/autosetup/ now required - https://sqlite.org/rsync.html very nice new replication tool
Given the direction in terms of building process upstream takes I'm starting to wonder if Turso/libsql is worth considering.
A comment on-topic regarding `sqlite3_rsync`: I was able to do the following without any problems, so presumably updating the port to create this executable and install it should be fine: cd /usr/ports/databases/sqlite3 sudo make build cd work*/sqlite* sudo make sqlite3_rsync sudo cp sqlite3_rsync /usr/local/bin Much appreciated if this could be added to the official package. Thanks.
Created attachment 265129 [details] v1 rebased for 3.50 SQLITE3, adds new default option for https://sqlite.org/rsync.html This is such a handy tool for doing backups or sync, that it's worth either a default option (as here), or a flavor. The disadvantage of a flavor is that other flavors would not have access to the tool, so I chose a default option. The various TEA/NO_TEA branches aren't clear to me, I hope the cases are covered correctly.
TEA is used if the databases/tcl-sqlite3 port gets built, which is the sqlite3 extension for the venerable Tcl programming language. Please check if this needs revision; we've updated sqlite3 to 3.50.4 to collect security fixes, and there the new 3.51.0 release has been out since Tuesday this week.
oh and don't forget to update the "Summary" of the bug or ask someone to do that next time.
^Triage: note that in general, we use "maintainer-feedback?" to notify maintainers, and do not assign the PR to them, on the theory that if they are not a committer, they cannot do the commit. Hat: bugmeister
+1 to enable this by default. It is a tiny helpful tool.