[Pkg-systemd-maintainers] Bug#719695: Bug#719695: Prefer symlinks over Alias= for non-matching service names

[Michael Biebl]

Package: network-manager
Version: 0.9.8.0-5

Am 14.08.2013 13:11, schrieb Michael Stapelberg:
> Package: systemd
> Version: 204-2
> Severity: normal
> 
> In case the name of a SysV init script does not correspond to the name
> of the systemd service file (e.g. /etc/init.d/network-manager, but
> /lib/systemd/system/NetworkManager.service, where the dash in the middle
> is the problem), we previously recommended people to use Alias=, e.g.
> Alias=network-manager.service in this case.
> 
> The issue with that is that the Alias= symlinks are enabled and disabled
> by systemctl enable|disable (also by deb-systemd-helper), whereas they
> should _always_ be present.
> 
> Upstream suggested to just use a symlink, so that is what I am
> proposing. In the case of NetworkManager, we should ship
> 
> /lib/systemd/system/network-manager.service -> NetworkManager.service
> 
> Any objections so far?

Sounds reasonable at first thought. I'll change the network-manager
packaging accordingly.

> In case of service files that contain an @ (for instances), e.g.
> stud at .service, we should ship a symlink that masks the SysV init script:

Do we have packages which only ship a templated service?


> /lib/systemd/system/stud.service -> /dev/null
> 
> Any objections? Otherwise I’ll go ahead and update the Systemd/Packaging
> wiki page with the best practice on that.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20130814/49dcd2bf/attachment-0002.sig>