@toots The liquidsoap-full dockerfiles are definitely a good start and I can
probably work backwards from there, but my question was whether it's possible
to use the OPAM-based installation (i.e. installing all of the LS dependencies
and LS itself via OPAM 2) to produce an installation that "looks and feels"
like one of the packaged builds, i.e. the binary is in `/usr/bin/liquidsoap`,
it's looking for `/etc/liquidsoap.conf`, that kind of stuff.
I currently have a Docker build based on OPAM 2 that works just fine in my
environment, but it contains all of Liquidsoap inside a folder alongside OPAM
itself, and it doesn't seem to be possible to separate the two.
This could definitely just be a limitation of the recommended OPAM installation
method, but it would be nice to take advantage of OPAM's flexibility and
built-in dependency resolving while producing something that others can use
downstream without much confusion.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/665#issuecomment-444577518
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
