Re: LMS for Windows using Strawberry Perl

> I'd like to revisit providing separate par-packer compiled binaries for
> each component.

Great!

> Is it necessary?

No. I'm even open to dropping all the helpers.

> What benefit does it provide over bundling a copy of
> the portable strawberry perl within the lms installer and running from
> the source?

"you have to install Perl" might scare people away. I think that really 
is it.

So I was wondering whether we could have two installers: the "full" 
version bundling Strawberry Perl with LMS. And the LMS only installer 
(used in updates), only installing the LMS code. I haven't looked into 
Strawberry Perl's licensing and what not. Just an idea.

> Setting up lms as a windows service works using 'NSSM'
> (https://nssm.cc/) running perl.exe, slimserver.pl and parameters
> directly in the service definition.

What's the licensing model there?

> Having perl and sources available on windows would bring the release in
> line with the other release flavours and allow code changes for
> troubleshooting issues.

Agreed.

> I can continue with the compiled binary builds but I'm not sure it the
> best option for the future.

If I may say so... I'd prefer you to work on a simple, stable 
installation procedure leveraging raw Strawberry Perl, than wasting time 
trying to figure out the issues with building binaries.

> I'd appreciate your thoughts on moving to a source based release.  The
> lms sources would still be stripped down to only what's needed for
> windows.

Great! An they would only be include once, not once per binary!

I know that you don't use Cygwin. But how are the chances that the build 
process would still work with Cygwin? It would be great if I didn't have 
to maintain another build host...