Hi Brian,
I just realized that my bug report, #792307, got merged with #863974
which may have the same underlying cause but a different interpretation
of the results. Yes, just installing the systemd binary won't enable it
as the active init system but another part of the dependency chain,
libpam-systemd, already imports some of the systemd patterns (separate
temp mount points for each user) which, apart from the incredible
clutter in the list of mounted file systems, breaks my workflows (I need
a single /tmp for all users).
Debian always maintained that systemd would be optional and I would hope
for a little more flexibility when it comes to [reasonable] requests to
allow setting up desktop systems without having systemd bits and pieces
getting in the way. Just having a version of policykit-1 compiled
without systemd dependencies would solve all our issues and it's a tiny
little change in the rules file. We would simply have two alternatives
for policykit-1, one with and one without systemd. Or dynamic support at
runtime. If there's anything I can do to help getting this implemented,
especially the runtime detection, please let me know - I'm more than
happy to put this together but only if I this is not a lost cause
because nobody is interested in accepting this as a patch, anyway.
Thanks,
--Christian
On 06/03/2017 09:57 PM, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the policykit-1 package:
#792307: policykit-1: There should be a variant of policykit-1 which doesn't
depend on systemd
It has been closed by Brian Potkin <claremont...@gmail.com>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Brian Potkin
<claremont...@gmail.com> by
replying to this email.
