net-dns/technitium-dns: ignore rm failure

The src_install() phase removes the built `systemd.service` in favor of
installing our own with fixed paths; the command is missing either `-f`
or `|| die` to clarify intent -- in this case, there is no harm if the
service file is not removed, since it won't be installed somewhere where
it would get picked up.

Signed-off-by: Itai Ferber <itai@itaiferber.net>
This commit is contained in:
Itai Ferber
2026-04-26 15:23:35 -04:00
parent 2f7fa34a3a
commit 792ce9378f
4 changed files with 4 additions and 4 deletions

View File

@@ -55,7 +55,7 @@ src_install() {
# The included `systemd.service` file has hard-coded paths we'd need to
# adjust; we'll install our own.
rm "${DOTNET_PKG_OUTPUT}/systemd.service"
rm -f "${DOTNET_PKG_OUTPUT}/systemd.service"
dotnet-pkg_src_install

View File

@@ -61,7 +61,7 @@ src_install() {
# The included `systemd.service` file has hard-coded paths we'd need to
# adjust; we'll install our own.
rm "${DOTNET_PKG_OUTPUT}/systemd.service"
rm -f "${DOTNET_PKG_OUTPUT}/systemd.service"
dotnet-pkg_src_install

View File

@@ -75,7 +75,7 @@ src_install() {
# The included `systemd.service` file has hard-coded paths we'd need to
# adjust; we'll install our own.
rm "${DOTNET_PKG_OUTPUT}/systemd.service"
rm -f "${DOTNET_PKG_OUTPUT}/systemd.service"
dotnet-pkg_src_install

View File

@@ -69,7 +69,7 @@ src_install() {
# The included `systemd.service` file has hard-coded paths we'd need to
# adjust; we'll install our own.
rm "${DOTNET_PKG_OUTPUT}/systemd.service"
rm -f "${DOTNET_PKG_OUTPUT}/systemd.service"
dotnet-pkg_src_install