[Pkg-systemd-maintainers] [Pkg-libvirt-maintainers] Bug#730604: libvirt-bin: Please rename libvirt-bin.service back to libvirtd.service and use symlink or Alias= instead
Laurent Bigonville
bigon at debian.org
Tue Jan 14 10:43:46 GMT 2014
Le Tue, 14 Jan 2014 11:14:41 +0100,
Guido Günther <agx at sigxcpu.org> a écrit :
> On Tue, Jan 14, 2014 at 10:08:58AM +0100, Laurent Bigonville wrote:
> [..snip..]
> > I'm not sure what you mean here. I don't think any changes on the
> > LSB initscript is required here.
> >
> > Renaming the .service file back to the original and adding a symlink
> > that matches the name of the initscript should be enough.
>
> We'd e.g. still have /etc/default/libvirt-bin used to configure the
> libvirtd service. THe package will also still be named libvirt-bin
> so I wonder if it wouldn't be more consistent to leave the service
> file as and add a
>
> Alias=libvirtd
I think it's a general good habit to keep the upstream file untouched.
And I don't think that the alias in this case is good (Alias= is lost in
case the service is disabled), a symlink will be needed anyway.
> so firewalld and others can reference it. I'm o.k. with renaming the
> whole package from libvirt-bin -> libvirtd in the future including
> unit files and init scripts but that's nothing I have time for atm.
>
> Patches to achieve this (and especially testing) would be welcome.
OK I'll add this to my todo list.
More information about the Pkg-systemd-maintainers
mailing list