I've got:
Running on a Raspberry Pi 4 with Alpine Linux 3.11.2:
Besides my bumbling (but ultimately successful) install with Fedora 31 on the Pi 3 B+, I don't have much experience with the installing LMS other than from the Windows installer or a Linux package of some sort.
I've read multiple posts on the subject like:
This guide by Roland0
This post by Stuarty
and this succinct one from Paul-
Paul-'s post doesn't mention needing slimserver-vendor. I guess I'm a little unclear still about the relationship between Perl versions, module versions, the two repos (slimserver-vendor and slimserver), and the various packages.
For this effort on Alpine, I mostly followed Stuarty's post above, basically:
- Cloned the slimserver-vendor repo and built the modules directly on the RPi4 with Alpine. This did require some minor edits here and there to get everything to build correctly. I can post my notes if anyone is interested.
- I also built the other binaries from the slimserver-vendor source (alac, faad, flac, sox, and wvunpack)
- Downloaded the "Logitech Media Server: Unix Tarball - No CPAN Libraries" archive and moved the modules under arch/5.30/aarch64-linux-thread-multi/ and binaries under Bin.
That seems to work ok, I can access the web interface, complete the setup, and stream music to a client. I haven't tested much beyond that.
I'm interested in feedback on whether this is a "good" process for getting a working LMS on an OS that doesn't have a pre-built package? My next step would be to try to get an APKBUILD together for it but I don't really want to go down that road until I have better feel for whether I'm taking the right build approach here or not. I've looked at some of Gentoo's ebuild files for LMS and they are a little scary (to me).
Based on Roland0's post, I *think* the main con to my current approach is that I'm tying the modules to the Perl version shipped on this release of Alpine which means that if Alpine updates Perl then that might break LMS?
Code:
Logitech Media Server (v7.9.2, 1576909043, Sat Dec 21 07:49:57 CET 2019) perl 5.030001 - aarch64-linux-thread-multiCode:
Linux rpi4 5.4.6-0-rpi4 #1-Alpine SMP PREEMPT Tue Dec 24 11:53:25 UTC 2019 aarch64 LinuxI've read multiple posts on the subject like:
This guide by Roland0
This post by Stuarty
and this succinct one from Paul-
Paul-'s post doesn't mention needing slimserver-vendor. I guess I'm a little unclear still about the relationship between Perl versions, module versions, the two repos (slimserver-vendor and slimserver), and the various packages.
For this effort on Alpine, I mostly followed Stuarty's post above, basically:
- Cloned the slimserver-vendor repo and built the modules directly on the RPi4 with Alpine. This did require some minor edits here and there to get everything to build correctly. I can post my notes if anyone is interested.
- I also built the other binaries from the slimserver-vendor source (alac, faad, flac, sox, and wvunpack)
- Downloaded the "Logitech Media Server: Unix Tarball - No CPAN Libraries" archive and moved the modules under arch/5.30/aarch64-linux-thread-multi/ and binaries under Bin.
That seems to work ok, I can access the web interface, complete the setup, and stream music to a client. I haven't tested much beyond that.
I'm interested in feedback on whether this is a "good" process for getting a working LMS on an OS that doesn't have a pre-built package? My next step would be to try to get an APKBUILD together for it but I don't really want to go down that road until I have better feel for whether I'm taking the right build approach here or not. I've looked at some of Gentoo's ebuild files for LMS and they are a little scary (to me).
Based on Roland0's post, I *think* the main con to my current approach is that I'm tying the modules to the Perl version shipped on this release of Alpine which means that if Alpine updates Perl then that might break LMS?