Upstream does supply a set of systemd unit files in the distribution tarball and an ability to control installation of those files through the --with/--without-systemdsystemunitdir option. The ebuild is currently unaware of these options, making installation of systemd units pkgconfig file dependant and thus automagic. The ebuild shall use systemd.eclass to handle installation of the systemd unit files in a clean and unified way. The preferred way to handle that is to use autotools-utils eclass, and call `systemd_to_myeconfargs' before `autotools-utils_src_configure', as in: inherit autotools-utils systemd src_configure() { local myeconfargs=( $(use_enable foo) --with-bar ) systemd_to_myeconfargs autotools-utils_src_configure } If you're not interested in migrating to autotools-utils, there is also a legacy `systemd_with_unitdir' function, which could be used like that: inherit systemd src_configure() { econf \ $(use_enable foo) \ --with-bar \ "$(systemd_with_unitdir)" } Currently introduction of the eclass will cause the package to install systemd unit files unconditionally. If you don't like that concept, feel free to take a vote on the appropriate gentoo-dev ml topic. The eclass behaviour might change in future.
Created attachment 280797 [details, diff] avahi-0.6.30-r301.ebuild.patch Attached is a ebuild for the master branch of the gnome-overlay. Works fine for me.
This bugs a bit old, and I'm not a systemd user. Nonetheless, if people want this, I'll add it. I just need testers to make sure its working with systemd.
I am using avahi and systemd, so testing is no problem.
I can confirm that this works on amd64. Shouldn't be a problem for other arches too, as it only installs the three .service text files into /usr/lib/systemd/system/. Having these files installed and adjusting them, if necessary, is much easier than searching the web for a draft. :) Thank you!
Okay I added this to avahi-0.6.31. Please test.
(In reply to comment #5) > Okay I added this to avahi-0.6.31. Please test. Works here, thank you!
