Attached you'll find a new ebuild for Mserv, a jukebox-style music server along with a few supporting files. This is my first ebuild submission, so please make constructive comments! I tried to keep everything fairly clean, but it ended up being more complicated than I expected. 1) Mserv expects to be run out of a user's home. Consequently I had to jump through some hoops to set it up as a system daemon. I opted for custom config files in the files dir over patching so a user can still run it out of her home dir should she wish. 2) I ran into a problem putting the apache service in the need line of the rc-script. Mserv will work with >=apache-1. However, apache-1 and apache-2 have rc-scripts with different names, so I have to do a little magic to adjust the need line to what the user has installed. 3) Mserv is released under a new license. There are some nice gui clients out there. I will submit a couple client ebuilds over the next few days. I suggest media-sound for all these ebuilds. Cheers!
Created attachment 17034 [details] mserv-0.35.ebuild
Created attachment 17036 [details] mserv-0.35-acl
Created attachment 17037 [details] mserv-0.35-config
Created attachment 17038 [details] mserv-0.35-initd
Created attachment 17039 [details, diff] mserv-0.35-mservplay.patch
Created attachment 17040 [details, diff] mserv-0.35-paths.patch
Created attachment 17041 [details] mserv-0.35-webacl
Created attachment 17043 [details] license
Created attachment 17098 [details] mserv-0.35.ebuild This ebuild cleans up the edit_need() function which worked, but only coincidently. It also removes a postinstall instruction that is no longer needed.
Hi, Maybe I've not correctly understood what this package does ... I think this is best broken up into seperate ebuilds; one to install the mserv application proper, and then seperate ebuilds for the clients available. Bug-wranglers, could you please re-assign to whoever looks after media-sound packages? Thanks, Stu
The package is a mp3 jukebox backend. The only client that gets installed is the default one that comes with the server. There are other clients available on the mserv website, but they are not included in the ebuild. In summary, the ebuild installs a server that listens on port 4444 for incoming requests. The server is in charge of playing the mp3s, managing the queue, picking random selections, etc. In order to communicate with the server (pick songs, vote, etc.), a user can telnet to 4444 directly, or use a gui client. The package includes one client, a perl cgi script, hence the apache requirement.
I really think this should be assigned to sound rather than web-apps. The only part of the package that has to do with the web is the default (sample) client. There are other clients out there that do not use the web (I'm writing a pyGTK one, myself). It is not necessary to use a web-based client, and it's really no more of a web-app than mysql w/ swat or cups. On the other hand, this is my first submission, so others know likely know better than I.
in portage
