The LMS is relatively often updated, whereas the PERL version is rather stable.
So I still think it would optimal if we could build scripts that allowed us to update the LMS directly independent from the PERL. Maybe pull the files from the tar ball or GIT - like described here: http://forums.slimdevices.com/showthread.php?99648-Howto-build-a-self-contained-LMS
I'll package up perl in it's own extension. I recompiled it last night to move it to path /usr/local/perl5/ The extension will probably just be called perl5.20.3.tcz Paths are all hard coded in perl, so as long as you call "/usr/local/perl5/bin/perl" it knows where everything is.
As for LMS
At home, on my main server, I have the full git tree downloaded, and I run LMS from that tree. When I want to update, I just run git pull.
What I did to run LMS in piCore, was just download the tarball from git, extract it. The CPAN files that are in the default git, work fine. Then edit the first line of both slimserver.pl, and scanner.pl to point at the special version of perl. Then start the system.
Is there any reason that we would not just build an extension with the latest LMS and then put the slimserver.conf and data folders in the backup set versus putting the whole tree in a persistant partition?