Hi Florian, I agree it's tricky to get the docs right.
On 2020-09-24 at 19:25:35, Florian Schlichting wrote: > Historically, the package has shipped a lot of infrastructure for > running as a system service, and I think having mpd run on a headless > box somewhere on the home network and being able to control one's music > remotely is one of its big appeals. That's closer to my use case, though not quite what I do. It's running on my desktop computer which I also use as a "home server". My goal is to have: - mpd working regardless of whether or not I am logged in - sound working for my user account (e.g. in vlc) without having to stop the mpd service That's probably not a reasonable default use case though. > However I feel most users would probably be served better by deleting all > of that infrastructure and configuring mpd to run from their user > session, just like their pulseaudio, which in my understanding is the > proper way to solve the permissions problem that Eduard mentions. That might be the way to go for the default. > Can we do sensible things for all of these use cases, or should we try > to do less but have that work out of the box? And what's the default use > case to be? I'm sure how to tackle all of this, but perhaps we should identify a few use cases and document them separately in the README. I can think of three: 1. systemd+pulseaudio in a user session 2. headless server 3. (whatever we call my use case) Francois -- https://fmarier.org/
