Bug#891810: hplip not installable without systemd
On Sun 04 Mar 2018 at 15:44:12 +0100, Didier 'OdyX' Raboud wrote:
> Le dimanche, 4 mars 2018, 13.54:27 h CET Jonas Smedegaard a écrit :
> > Is PolicyKit _required_ for _all_ uses of hplip?
>
> Good question. I'll admit I was put off my the (exhausting) 'systemd'
> argument, and hadn't checked what exactly was done with PolicyKit.
>
> My reading is that PolicyKit is used to grant privilege to run `hp-plugin` for
> plugin download, thereby avoiding the need for sudo.
>
> So no, definitely not _required_.
>
> > Otherwise I believe hplip should only recommend policykit: The purpose
> > of "Recommends" is to permit "exotic" uses, which I believe this is -
> > unless hplip *cannot* work *at* *all* wothout PolicyKit in place.
>
> We don't agree on what constitutes "exotic" use of hplip. Oh well… I suspect a
> Recommends is good enough. I'll upload that demotion later today. Just don't
> expect that demotion to withhold too many "I can't run hp-plugin" bugs. :)
Most users install recommended packages. Those that don't (like me)
have to face the consequences.
Moving to something else brought up in this report: is it really
necessary for the hpps filter to be in hplip? Could it not be put
in printer-driver-postscript-hp as is done for the filter hpcups
in printer-driver-hpcups. (And - if you are in an energetic mood :)
there is #890930 too).
Regards,
Brian.
Reply to: