What are some of the challenges in refactoring buildme.sh to support future perl versions when they're released? I mean, I understand how
The main challenge is that we don't know the future and what the future brings :-). What the script shows is that it was basically created for a one-off action: build a few binaries to be distributed and hopefully never needed to run again.
The script has some logic to figure out where the perl distribution is installed. That code isn't very smart and could definitely see some added smarts. Then there's a lot of duplicated code, only difference being variable names for different perl versions.
I'm sure this could be simplified. But as this is supposed to be a script which is run once by one guy, then forgotten, nobody cared...
older versions of SC/SBS/LMS used different versions of different CPAN modules who's source may not have aged well..i.e. buildme.sh for SC 7.3.1 is likely broken with perl 5.14.2. But couldn't there be a generic version of buildme.sh that at least *tries* building the modules with a new perl version and a new architecture? Or does it do that already?
It does it, but wouldn't find the newer perl. That's probably a starting point.
-- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
