Use Liquidsoap DEB as default for native installation
I've clarified with Romain, maintainer of Liquidsoap the pros and cons with OPAM vs DEP installation.
For end users and development flow (updates), it's much more straightforward using the DEB build provided on GitHub.
Asking about the disadvantages I got this answer:
The real potential issue with the build is that they enable virtually all available features. This increases the risk for potential issues such as segfault, memleak and etc. I'd say, if your priority is limiting user friction then by any means go for it. If you can, however, identify a stable sub-set of features that you will need then either install via opam or perhaps build your own .deb. It wouldn't be too, too crazy to enable specific GH workflows with limited subsets of optional deps built in either, you could fork our main repo and do that. I'll see if I can find a way to parametrize ours to make it easier.
Since the Docker build is also enabling all default features, I'd opt for UX/DX priority at first. As soon we face any issues we might rethink that approach.