> Hi Alexandre, > > thanks for your fast answer and correctly guessing my Distribution ,-) > > (if this is off-topic in systemd-devel, which I suspect, please feel > free to reply in private mail instead).
Oops, I just tought I was reading other list [email protected] ; you can send your dh_systemd specific questions there. Im' subscribed > > > This works as designed. Unfortunately, my Distribution's build tools > > > don't handle package-provided targets too well, and I feel that using > > > a target here is kind of wrong anyway. > > > > Hi, > > > > Package-provided targets works well, > > but by default debhelper will try to enable everything. > > My debian/rules is: > override_dh_installinit: > dh_systemd_enable -pisc-dhcp-server --name=isc-dhcp-server-v4 > dh_systemd_enable -pisc-dhcp-server --name=isc-dhcp-server-v4-old > dh_systemd_enable -pisc-dhcp-server --name=isc-dhcp-server-v6 > dh_systemd_enable --verbose -pisc-dhcp-server > --name=isc-dhcp-server.target > dh_installinit -Nisc-dhcp-server > dh_installinit -pisc-dhcp-server --error-handler=true I wouldn't mix "systemd" stuff under a sysV rule, but under a separate systemd rule then If you only need to enable the target that would pull the 2 or 3 services, so this is basicaly enough: override_dh_installinit: dh_installinit -pisc-dhcp-server --error-handler=true override_dh_systemd_enable: dh_systemd_enable -pisc-dhcp-server isc-dhcp-server.target --- Well, are you even using "dh --with systemd" ? In theory, it's possible to use dh_systemd_* directly, but that's mostly useless pain. https://wiki.debian.org/Teams/pkg-systemd/Packaging says *) If you are using plain debhelper, make sure to run dh_systemd_enable *before* dh_installinit and dh_systemd_start *after* dh_installinit _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
