Fletch wrote: > robinbowes;239059 Wrote: >> Personally, I think some of the files are in the wrong places. >> >> Why are the server and scanner programs in /usr/sbin? squeezecenter >> will not run as root. Surely these should be in /usr/bin or possibly >> /usr/libexec? > > ;) I'm sure you recall a discussion last year between you, me, Al > Pacifico and Dan Sully about this. I still agree with you. I gave in > to /usr/sbin because: > - other packages like httpd and smbd that don't run as root are in > /usr/sbin
Ah, but they bind to privileges ports so need to start as root. slimserver does not. > - Dan wanted to be consistent with the Debian package That's just wrong - this is not a debian package. It is an RPM for use on Redhat-flavoured systems. It should follow Redhat packaging guidelines. I would put it in /usr/libexec (actually, I would put the whole lot in /opt, and /var/opt but I've lost that battle!! :) ) > Feedback from other interested parties would be great. > >> Why is the CPAN dir in /usr/share/squeezecenter? Surely that should go >> under /usr/lib/perl5 somewhere? > > I'm not really a perl guy. Since everything in CPAN and lib are perl > modules that could also have other versions under /usr/lib/perl5, do we > really want the SC stuff in @INC? This is also why I used "Autoreqprov: > no". Hmmm. Well, the O/S CPAN dir goes in /usr/lib/perl5/5.8.8/CPAN. The Slim stuff could go in /usr/lib/perl5/site_perl/5.8.8/CPAN or even /usr/lib/perl5/site_perl/5.8.8/Slim/CPAN What does "Autoreqprov" do? > >> Hmmm, it's a noarch RPM but contains the CPAN/arch tree containing i386 >> and x86_64. That doesn't seem right. > > I hope they also add ppc and other arches. What's the packaging > alternative? SD will not want to have different arch packages. If the > RPM is installed on an arch not in CPAN/arch, the user just needs to run > "build-perl-modules.pl". Otherwise it "just works". If arch-specific code is included in the RPM then it should be an arch-specific RPM. So I guess this means separate i386 and x86_64 RPMs. In fact, it's arguable that the rpmbuild process should run build-perl-modules to create the arch-specific files on the platform on which the RPM is being built. > >> I think the MySQL stuff should go in /var/lib/squeezecenter (not >> /var/cache/squeezecenter) and it should also get a separate subdir, >> i.e. /var/lib/squeezecenter/mysql. > > I agree this is messy. I disagree on the mysql stuff since it can > always be recreated via the scanner. True, but the MySQL RPM puts the default DB under /var/lib. I'm just following precedence. > IMO, a worse problem is that some > plugins will write opml files to the cachedir. These willl be lost > foreer if the cachedir goes away. For this reason, maybe the entire > cachedir should go in //var/lib/squeezecenter. Hmmm. Well, that might not be a bad idea. I've just checked how I've got my manual install laid out and it seems I also end up with the DB and opml files under the cache dir (/var/opt/slimserver/cache/trunk in my case). I've not worried to much about it previously as I use the system MySQL, not the one that comes with the squeezecenter. The ideal solution would be to sort out the mess and put the stuff that is "valueable" in /var/lib/squeezecenter and everything else in /var/cache/squeezecenter. I'm not sure how feasible that is. Oh, and the pref file should definitely go in /var/lib/squeezecenter, *not* in /etc/squeezecenter. I'll get back to you about the SELinux stuff when I've sorted it. R. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
