* Bill Moseley shaped the electrons to say...
Where do bugs get posted?
http://bugs.slimdevices.com/
$ cat server.log File /home/moseley/music/beatles/sgt_peppers_lonely_hearts_club_band/beatles - sgt_peppers_lonely_hearts_club_band - 01 - sgt_peppers_lonely_hearts_club_band.ogg does not exist or cannot be read. at /home/moseley/SlimServer_v2005-03-15/CPAN/Ogg/Vorbis/Header/PurePerl.pm line 27, <GEN7> line 1.
It's true, that file does not exist. The true path is this:
/home/moseley/music/Beatles/sgt_peppers_lonely_hearts_club_band/beatles - sgt_peppers_lonely_hearts_club_band - 01 - sgt_peppers_lonely_hearts_club_band.ogg
Is someone developing on Windows where case dosen't matter?
No.. we're very case sensetive. Is that path a network share by any chance?
By the way, a few questions tracking the devel code -- basically looking for tips to make trying different versions easier.
1) Can I download a "slim" version of slimserver that doesn't include all the perl dependencies (CPAN files) and use the ones on my system instead?
http://www.slimdevices.com/downloads/nightly/latest/6.0/SlimServer_v2005-03-15.no-cpan-arch.tar.gz
2) Is there anonymous cvs that might make updating easier?
We use Subversion.
http://www.slimdevices.com/dev_resources.html#subversion
3) Any tricks to managing (keeping) the config files when, say, upgrading to a new nightly build. That is, what files can I put in a stable location when trying different nightly builds?
By default on a *nix system, the pref file will go in $HOME/.slimserver.pref - which stays there unless you remove it.
4) Any way to have a common plugins directory used for different versions? I currently symlink to the plugins I use, but it would be better to have that picked up automatically.
Not really. Most plugins are version dependent.
-D _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
