Make biber survive calls to strip

[lemzwerg]

It would be great if the biber binary survived

strip biber

just as a safety measure. Alternatively, biber could ask the user at a fatal error at the very beginning of execution whether the binary was accidentally stripped.

As an example, biber --help showed

Perl lib version (5.26.3) doesn't match executable
  'perl' version (5.26.1) at
  /opt/local/lib/perl5/5.26/darwin-thread-multi-2level/Config.pm line 62.
Compilation failed in require at /opt/local/lib/perl5/site_perl/5.26/PAR.pm line 7.

after accidental stripping – I wasn't aware that biber comes with its own Perl interpreter, and after hours of investigation I was still not able to find out why my installed PAR bundle reports issues due to different perl versions...

[plk]

I think this is unlikely - biber isn't a normal .exe (it is a PAR exe) and is also specially modified to allow it to be signed on OSX. I might be able to design a warning about stripping but this is the first time in years anyone has tried to strip it ...