1. All modules specific (modified) to LMS MUST stay in /lib. Is that correct?
Yes.
2. /CPAN contains 'stock' modules, NEVER modified one because LMS, they MUST stay in /lib (see 1). Is that correct?
Yes.
The question then is: how, in LMS (not in a plugin) we handle situations where LMS should use a different .pm in different archs or versions?
As you saw in the search path list: LMS would first check the platform specific locations in CPAN, and only then lib.
Audio::Scan
That, unfortunately, is somewhat of an ugly exception. The fact that it's in lib, as well as in CPAN, is due to an early attempt of mine to not have platform specific files. I hoped one Audio.pm file would be good enough to cover them all. Later on I gave up that idea and put a copy of that file in all required folders.
in /lib we have a version that is good only until PERL 0.24, then we have specific versions in CPAN (are they 'stock'?) for 5.26, 5.28 and 5.30, but if I look at the system CPAN of 5.30 in arch, I should use version 1.01 NOT 1.02, then I'll need: Solution 1: an arch specific Audio/Scan.pm (is that working with boostrap.pm ?) Solution 2: a modified Audio/Scan.pm in lib in order to handle the loading of different Scan.so depending on versions (in the style of the current one, but evolved to 10.1 and 1.02).
Don't try #2. It turned out to be difficult. -- Michael _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
