1 | So, you want to develop gutenbach, eh? Good! |
---|
2 | |
---|
3 | Gutenbach is a distributed music player built on top of CUPs. It |
---|
4 | essentially enables anybody with access to it to play music from their |
---|
5 | own computer -- all they have to do is "print" to the Gutenbach |
---|
6 | instance as they would any other document! |
---|
7 | |
---|
8 | The current repositories for various Gutenbach features are: |
---|
9 | - gutenbach |
---|
10 | - gutenbach-queue |
---|
11 | - gutenbach-remctl |
---|
12 | - gutenbach-rhythmbox-plugin |
---|
13 | - gutenbach-itunes-plugin |
---|
14 | - gutenbach-web |
---|
15 | |
---|
16 | All of these are located on GitHub: |
---|
17 | http://github.com/search?langOverride=&q=gutenbach&repo=&start_value=1&type=Repositories |
---|
18 | |
---|
19 | Additionally, see README.old for how Gutenbach /used/ to be installed. |
---|
20 | This can sometimes offer insight into how to fix things that are |
---|
21 | broken. |
---|
22 | |
---|
23 | Questions or comments should be directed at gutenbach@mit.edu |
---|
24 | |
---|
25 | TODO: |
---|
26 | - include mixer and channel in debconf, or even better, move it to |
---|
27 | gutenbach-remctl and implement debconf in that package |
---|
28 | - the filter should die and send an error message if it can't find the |
---|
29 | config file, not use defaults |
---|
30 | - this should really not conflict with pulse |
---|
31 | - finish the move to CUPS! |
---|
32 | * the CUPS daemon processes do not inherit groups from the lp user (so, for example, |
---|
33 | even if we add 'lp' to 'audio', the process will not be running in group 'audio'). |
---|
34 | For the time being, I've set the CUPS daemon to always run under group 'audio', |
---|
35 | but there should really be a better solution. |
---|
36 | * lprm does not remove jobs -- we should maybe leave a pid file and kill the mplayer |
---|
37 | process if someone kills the job |
---|
38 | * you can currently play files locally, but not remotely -- why? |
---|