Sign in

Search issue titles and bodies, change requests and comments. Private repositories you cannot read are not included.

vole
Clone

Read only, no credentials:

https://rodent.software/git/vole.git

Write over SSH with a registered key:

git clone ssh://git@0.0.0.0:2222/vole.git

A free and open-source forge that lives in your Git repo.

Ask the build for FTS5

41dd571fae2d00dab2f7bc4a2299e220a134fa13 · Keenan Nemetz · 10d ago · parent 72f22292

Ask the build for FTS5

Search needs SQLite's FTS5 module. The driver's bundled SQLite only
compiles it in with a build tag, so every build and test command that can
reach the index now passes `sqlite_fts5` beside `libsqlite3`: the verify
and release images, both workflows, and the commands the docs give for
building and testing from source.

With the system library the tag is inert — the module is whatever the
distribution built — and the packages already depend on that library.
Debian, Ubuntu, Fedora, RHEL and Rocky all enable FTS5, and
docs/packaging.md now says the dependency includes it.

CONTRIBUTING.md +2−2

@@ -157,8 +157,8 @@ That workflow runs formatting, vet, build, the license check, reachability
157 157 scanning, packaging, link checks, and the race test suite. If it cannot run
158 158 locally because no container runtime is available, run the relevant underlying
159 159 commands with the same flags the image sets
160 (`CGO_ENABLED=1 go vet -tags libsqlite3 ./...`,
161 `CGO_ENABLED=1 go test -tags libsqlite3 -race ./...`) and say which check you
160 (`CGO_ENABLED=1 go vet -tags libsqlite3,sqlite_fts5 ./...`,
161 `CGO_ENABLED=1 go test -tags libsqlite3,sqlite_fts5 -race ./...`) and say which check you
162 162 could not run.
163 163
164 164 Fuzz targets live beside the parsers and validators they drive — `server/ssh`,