SlimServer is a streaming music server for use with Slim Devices' SLIMP3 and Squeezebox (see http://www.slimdevices.com/). It can also be used to stream music to other computers. An ebuild was created for an older version of the software in Bug #30721. The ebuild was never accepted into portage. I would like the focus of this bug to be getting this package accepted into portage. I have updated the original ebuild from Bug #30721 to use the latest version of the SlimServer software, as well as added USE flags and Runtime Dependencies for flac and oggvorbis. A couple of questions: right now the ebuild has slot 0. Should the slot of the ebuild match the major version of the package even if no older versions exist in portage, or should the slot always start at 0 for the first version of the package to appear in portage? Second, SlimServer can only stream mp3 and PCM audio, and PCM audio can only be streamed to Squeezebox. SlimServer uses lame to transcode oggvorbis and to encode flac to stream to SLIMP3. SlimServer only needs to transcode oggvorbis and decode flac to stream to Squeezebox. Right now I have RDEPENDed lame when the flac and oggvorbis USE flags are set. However, if the user has aiff or wav files they will still need lame to encode files to stream to SLIMP3. The ebuild doesn't catch this by only depending on lame of the flac or oggvorbis USE flags are set. Should the ebuild ALWAYS depend on lame even though it might not be used? Reproducible: Always Steps to Reproduce:
Created attachment 33024 [details] Ebuild, conf and rc files.
SLOT=0 is what it should be until incompatibilities crop up.
I just tried this with the 5.2.0 version of the slimserver software (using a straight copy of the 5.1.5 ebuild) and it works fine on my x86 box (I unmasked the x86 build to avoid updating any other bits of software).
Created attachment 34526 [details] slimserver-5.2.0 archive Updated the archive to contain a slimserver-5.2.0 ebuild and digests.
A question and a note: Question: what category do people think this ebuild belongs under? I have been keeping it under net-misc. Note: Since I'm not sure what the status of this package getting into portage is, I am going to try breakmygentoo to see if they will host it (as soon as their Bugzilla mails me my password :O) I think this package is mature, stable, and useful enough to belong in Portage though--I don't know why it is taking so long.
Speaking purely as a user of gentoo, my 2c's worth is that I'd expect it to go under media-sound since sound, more than the networking, is what's important to me.
I opened a breakmygentoo bug (http://bugs.breakmygentoo.net/show_bug.cgi?id=426) to see if they will host the ebuild since there hasn't even been a response as to why this package hasn't been acccepted into Portage, or what needs to be done for it to happen. I agree with Doug that media-sound also makes sense for the category. I think it is ambiguous though which is why I'd like to hear what people have to say. I would be satisfied either way so we might as well choose what most people agree on.
I think it should go under media-sound as well. Anybody have any ideas on when this will make it into portage? Slimserver is up to v5.3.0 now as well if anyone is interested.... Notable changes included in SlimServer 5.3.0: * Major firmware upgrade focused on stability and performance; * Support for a variety of proportional fonts and animation for the new graphic display; * A wide variety of improvements to the web and player user interface; * Built-in RadioIO Internet Radio.
Created attachment 40418 [details] slimserver-5.3.0.ebuild This bug has been open for nearly five months now and slimserver *still* has not made it into portage--what's the deal? Breakmygentoo doesn't want it, and why should they since this package has been tested by dozens of people and is stable by now. I have received emails from several people asking why slimserver isn't in portage yet. Unfortunately I am not a dev so there isn't much I can do about it. If someone wants to give me CVS access I would be glad to check it in myself. If this ebuild isn't in portage by 00:00 UTC on September 27th (Sunday night) I am going to bug the whole gentoo-dev list about it. Thank you, -Chris Sachs
Created attachment 40419 [details] /etc/conf.d/slimserver updated for 5.3.0
Created attachment 40420 [details] /etc/init.d/slimserver I was ridiculed on breakmygentoo's bugzilla for not attaching everything as text files. Now there should be no excuses not to put slimserver into portage :O)
Created attachment 40421 [details] slimserver-5.3.0.ebuild -- minor tweak Fixed ebuild to not try to update your /etc/slimserver.conf with a blank file when you upgrade. --- slimserver-5.3.0.ebuild.old 2004-09-26 01:58:20.383917528 -0700 +++ slimserver-5.3.0.ebuild 2004-09-26 01:58:41.825657888 -0700 @@ -29,7 +29,6 @@ insinto /etc/conf.d && newins "${FILESDIR}/slimserver.conf.d" slimserver exeinto /etc/init.d && newexe "${FILESDIR}/slimserver.init.d" slimserver - touch ${D}/etc/slimserver.conf } pkg_postinst() {
5.3.1 is out. ebuild bump didnt create a /etc/conf.d/slimserver file. devs, any word on this?
works. ignore my last comment as i missed the conf and init files. simple version bump to 5.3.1 works.
Working well for me too.
marking this one as a duplicate since the other bug provides a more recent ebuild for slimserver. *** This bug has been marked as a duplicate of 73832 ***
