Latest LMS 8.4 on macOS 10.15 falls back to perl 5.18

[AF1]

I see. Don't know about the entire 10.10 - 10.15. It's a very long time with a lot of changes. I never had any problems with your 5.34 on 10.15 though.
I wasn't worried about performance. Since pCP and other builds use more recent perl versions, I think that by sticking to 5.18 to test my plugins, I might miss some changes (deprecations...). When I still used 5.18, some users had soem problems I don't remember on pCP (it used 5.28 at the time I think).

Can you point me to where you actually force 10.x to use the dated 5.18? Unless it's not in a perl script etc. and you excluded this when you compiled the binary.
Thanks.

[mherger]

Latest LMS 8.4 on macOS 10.15 falls back toperl 5.18

> After installing Dec 4's LogitechMediaServer-8.4.0-*1670141288* on my
> mac *10.15*, LMS started using the default perl 5.*18* again (BTW 10.15

That's correct: some older macOS versions would not run with binaries I
created. So I decided to keep things simple and only use those on macOS
11 going forward. macOS 10.x will continue to use perl 5.18.

In most cases this should have no impact at all. I wouldn't expect my
build to be faster or whatever.

[AF1]

Latest LMS 8.4 on macOS 10.15 falls back to perl 5.18

Hi.

After installing Dec 4's LogitechMediaServer-8.4.0-1670141288 on my mac 10.15, LMS started using the default perl 5.18 again (BTW 10.15 is the last version my mac supports, so no upgrade option).
$PATH = /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
There's a symlink in "/usr/local/bin" to the perl version in the LMS pref pane package.
"which perl" shows "/usr/local/bin/perl", so macOS should use this symlink.
But it doesn't.

Then I reinstalled a previous 8.4 version: LogitechMediaServer-8.4.0-1667630687
That worked. Now LMS uses the symlinked perl 5.34 from the LMS pref pane package again.

Have there been any changes between 1667630687 and 1670141288 concerning perl (scripts) or such that would explain this? I can't make sense of this, yet.
Thanks.

[AF1]

> Can you point me to where you actually force 10.x to use the dated
> 5.*18*? Unless it's not in a perl script etc. and you excluded this when
> you compiled the binary.

It's in the executable file's header:

% head
/Library/PreferencePanes/Squeezebox.prefPane/Contents/server/slimserver.pl
#!/Library/PreferencePanes/Squeezebox.prefPane/Contents/perl/bin/perl

you can replace this with

#!/usr/bin/perl5.18

Or simply run

% /Library/PreferencePanes/Squeezebox.prefPane/Contents/perl/bin/perl
/Library/PreferencePanes/Squeezebox.prefPane/Contents/server/slimserver.pl

on the command line when you want to try "our" Perl temporarily. This
allows you to easily switch between the Perl versions for testing purposes.