commit: 98979ea97a7ce6a93d46418421be09443c4afbcb
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 6 14:45:46 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Sep 6 14:46:21 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=98979ea9
Revert "net-misc/kea: Stop old kea service on upgrade to >= 3.0"
This reverts commit 8078688abb58c9301fc88dcedef32e5549c5f499.
I thought about it some more and I think it goes against the principle
of least astonishment, even if I think it's well-intentioned and not
a bad idea. I think it's better to let users kill it than stop it
(and not start it again).
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-misc/kea/kea-3.0.1.ebuild | 15 ---------------
1 file changed, 15 deletions(-)
diff --git a/net-misc/kea/kea-3.0.1.ebuild b/net-misc/kea/kea-3.0.1.ebuild
index f20e465cd90f..cd42501a703e 100644
--- a/net-misc/kea/kea-3.0.1.ebuild
+++ b/net-misc/kea/kea-3.0.1.ebuild
@@ -268,21 +268,6 @@ src_install() {
fperms 750 /var/lib/${PN} /var/log/${PN}
}
-pkg_preinst() {
- if ver_replacing -lt 3.0; then
- if [[ ${ROOT} ]]; then
- return
- elif [[ -d /run/openrc ]]; then
- # There is no easy way to automatically switch to new
init.d kea scripts, so we have to stop the
- # old kea service if running otherwise the user will
find it is not possible stop the old kea
- # service post install
- ebegin "Previous kea service will be stopped"
- rc-service -q --ifstarted --nodeps kea stop
- eend $?
- fi
- fi
-}
-
pkg_postinst() {
tmpfiles_process ${PN}.conf
