Paul Holzinger e5b876571b Makefile: use libsqlite3 build when possible ... Dynamically link sqlite3 when installed, the main motivation is that we reduce the podman binary size with that. I see about 3.2 MB savings. But also dynamically linking it means if there a vulnerabilities only the sqlite3 distro package needs updating and we don't have to make a new podman release with the vendored update. Signed-off-by: Paul Holzinger <pholzing@redhat.com>		2025-06-11 10:31:53 +02:00
..
Dockerfile	run container-diff tests in Travis	2018-09-12 13:37:11 +00:00
apparmor_tag.sh	Add automatic apparmor tag discovery	2019-08-05 12:22:25 +00:00
build_speed.sh	Spelling	2020-12-21 16:47:18 -05:00
check_vendor_toolchain.sh	Finish updating to go 1.22	2024-11-11 11:03:11 -05:00
get_ci_vm.sh	Fix use generic/ambiguous DEBUG name	2022-06-02 11:44:38 -04:00
libsubid_tag.sh	build: fix test for subid 4	2022-06-21 19:40:07 +02:00
sqlite_tag.sh	Makefile: use libsqlite3 build when possible	2025-06-11 10:31:53 +02:00
systemd_tag.sh	Makefile: build with systemd when available	2022-02-14 10:05:35 +01:00
tree_status.sh	make vendor-in-container	2021-08-04 15:23:11 -04:00
xref-helpmsgs-manpages	[CI:DOCS] man pages: sort flags, and keep them that way	2022-03-24 08:27:06 -06:00