Michael Stapelberg <[email protected]> writes: > Hi Joey, > > Thanks for the quick review. > > Joey Hess <[email protected]> writes: >> The only questionable part seems to be the direct use of of >> /etc/systemd/system/. Is there a consensus that this is the right thing >> to do? I see symlinks being dropped in there by many packages >> currently. > I talked to mbiebl and Mithrandir about it and we’ve come to the > conclusion that we want to ship the files in /lib instead (for > consistency with upstream packages and other distributions) and maybe > work on UCF support for this location instead of shipping the service > files in /etc.
Another option could perhaps be to ship the files in /lib, but instead of relying on UCF or some other kind of mechanism to fiddle with the symlinks in /etc, ship files there too. Files that do nothing but .include the file in /lib. Things like: .include /lib/systemd/system/foo.service The advantage of this is that the whole conffile handling is left up to dpkg, no other mechanism is needed, neither in maintainer scripts, nor elsewhere. Users can still modify the files, or even remove them: it will be handled correctly. In most cases, they can even leave the .include there, and just override the few things they need to override. (and dh_installinit could then perhaps assist with creating these .include-only files automatically, based on what the package installs under /lib/systemd) -- |8] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
