Hi, On Mon, Jul 06, 2015 at 10:45:43PM +0200, Jan-Benedict Glaw wrote: > Hi all, hi Guido! > > I just wanted to throw in my 2c. While cleaning up some machines, I > came along my KVM host and actually wondered why policykit was pulled > in. I'm as well only using root-based access to libvirt, which keeps > all the systemd stack installed. > > I admit that I'm not too deep into the details of packaging. It's > probably a good thing to pull polkit in the first place, since it's > probably used. However, I'd be quite happy to see a way getting rid of > the (hard) dependency, allowing to deinstall polkit and its > dependencies. Going a route like requiring some libvirt-auth meta > package, provided by libvirt-polkit und libvirt-socket would probably > do the job, but might look like over-engineering?
I do agree that being able to go without polkit would be nice but a similar situation with virt-manger showed that Recommends: are just not enough. Many people skip them and then report bugs if you use Recommends for a package that's needed in 95% of the installations. I'm just not up to handle these. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
