ssods-3.21 (now 3.22) is for 7.4-trunk. It doesn't work for 7.3.x
because there are a couple of too new Perl modules in it.

ssods-3.18 should be used with 7.3.x.

I adjusted the text on my page accordingly.

I still have some strange issues with some versions of 7.4:

SC works. scanner doesn't work:


Code:
--------------------
    
  f...@ds508 ..sik/SqueezeCenter-7.4-svn $ ./scanner.pl --help
  Global symbol "%GetInfoType" requires explicit package name at 
/volume1/flip/Musik/SqueezeCenter-7.4-svn/Slim/Utils/MySQLHelper.pm line 590.
  Compilation failed in require at (eval 117) line 2.
  BEGIN failed--compilation aborted at (eval 117) line 2.
  Log4perl: Seems like no initialization happened. Forgot to call init()?
  
--------------------


However, if I apply the following patch it does work!


Code:
--------------------
    
  -- scanner.pl  2009-08-06 22:01:04.000000000 +0200
  +++ scanner.pl-ok       2009-08-06 22:01:01.000000000 +0200
  @@ -45,7 +45,7 @@
  use Slim::bootstrap;
  use Slim::Utils::OSDetect;
  
  -       Slim::bootstrap->loadModules([qw(version Time::HiRes DBD::mysql DBI 
HTML::Parser XML::Parser::Expat YAML::Syck)], []);
  +       Slim::bootstrap->loadModules([qw(version Time::HiRes DBI DBD::mysql 
HTML::Parser XML::Parser::Expat YAML::Syck)], []);
  
  require File::Basename;
  require File::Copy;
  
--------------------


I've got no idea why the order of loading the HTML::Parser and
XML::Parser::Expat makes a difference.

Anybody?


-- 
flipflip

Check out flipflip's 'SlimServer On DiskStation (SSODS)'
(http://oinkzwurgl.org/ssods/)!      Please do NOT file SSODS bugs in
(SC's) bugzilla. Use the forums. And only the forums. Thanks.
------------------------------------------------------------------------
flipflip's Profile: http://forums.slimdevices.com/member.php?userid=5223
View this thread: http://forums.slimdevices.com/showthread.php?t=66063

_______________________________________________
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta

Reply via email to