registry and hence is well suited to run anything from the root
zone, the top-level domain, to many smaller standard domain names.
-Package: redis-knot
+Package: redis-module-knot
Architecture: any
Depends:
${misc:Depends},
+++ /dev/null
-usr/lib/*/knot/redis/knot.so usr/lib/redis/modules/
--- /dev/null
+usr/lib/*/redis/modules/knot.so
--libexecdir=/usr/lib/knot \
--with-rundir=/run/knot \
--with-moduledir=/usr/lib/$(DEB_HOST_MULTIARCH)/knot/modules-$(BASE_VERSION) \
+ --with-redisdir=/usr/lib/$(DEB_HOST_MULTIARCH)/redis/modules \
--with-storage=/var/lib/knot \
--enable-systemd=auto \
--enable-dnstap \
echo "Stripping the QUIC symbols"; \
sed -i '/knot_quic_/d' $(LIBKNOT_SYMBOLS); \
fi
- @if [ -f "$(CURDIR)/debian/tmp/usr/lib/*/knot/redis/knot.so" ]; then \
- chmod 0755 $(CURDIR)/debian/tmp/usr/lib/*/knot/redis/knot.so; \
+ @if [ -f "$(CURDIR)/debian/tmp/usr/lib/*/redis/modules/knot.so" ]; then \
+ chmod 0755 $(CURDIR)/debian/tmp/usr/lib/*/redis/modules/knot.so; \
fi
override_dh_auto_install-indep:
%description -n python3-libknot
The package provides Python bindings for the libknot shared library.
-%package -n redis-knot
-Summary: Redis module for Knot DNS.
+%package -n valkey-module-knot
+Summary: Valkey module for Knot DNS.
Requires: %{name}-libs = %{version}-%{release}
-%description -n redis-knot
-The package provides Redis module for Knot DNS.
+%description -n valkey-module-knot
+The package provides Valkey module for Knot DNS.
%package doc
Summary: Documentation for the Knot DNS server
--libexecdir=/usr/lib/knot \
--with-rundir=/run/knot \
--with-moduledir=%{_libdir}/knot/modules-%{BASE_VERSION} \
+ --with-redisdir=%{_libdir}/valkey/modules \
--with-storage=/var/lib/knot \
%{?configure_db_sizes} \
%{?configure_quic} \
%{python3_sitelib}/libknot
%{python3_sitelib}/libknot-*-info
-%files -n redis-knot
-%attr(0755, root, root) %{_libdir}/knot/redis/knot.so
+%files -n valkey-module-knot
+%attr(0755, root, root) %{_libdir}/valkey/modules/knot.so
%files libs
%license COPYING
must be configured carefully to avoid conflicts or unexpected interactions.
On the database side, the ``knot`` module must be available (e.g. by installing
-the ``redis-knot`` package from a `repository <https://www.knot-dns.cz/download/>`_)
-and loaded into the database. This is usually done by adding the following
-line to the database configuration::
+the ``redis-module-knot`` or ``valkey-module-knot`` package from
+a `repository <https://www.knot-dns.cz/download/>`_)
+and loaded into the database. This is usually done by adding one of the following
+lines to the database configuration::
- loadmodule /usr/lib/redis/modules/knot.so [<parameter> <value>]...
+ loadmodule /usr/lib/x86_64-linux-gnu/redis/modules/knot.so [<parameter> <value>]...
+
+or::
+
+ loadmodule /usr/lib64/valkey/modules/knot.so [<parameter> <value>]...
where the optional module parameters are: