0002796: Enable pipe output by default

(0005310)
qball (administrator)
2010-02-01 03:53

Why? Motivation would be nice!!

(0005313)
jeffayle (reporter)
2010-02-01 10:31

If you insist! (Not sure if I can edit this into the ticket)

The reason I want pipe output enabled by default is so that it will make its way into distribution repositories like that. The other day, I downloaded the latest source so that I could compile it myself with pipe support, which didn't work out too well because I couldn't get Ubuntu to install liblame or libwavpack, so I only ad flac support.

Now, the advantage of having pipe output would be that anyone could make a new output plugin, which would mean that MPD could do some really cool stuff. For example, the reason I went and compiled it myself was so that I could use a pipe output to stream to airtunes, which I got (somewhat) working in less than half an hour.

(0005314)
qball (administrator)
2010-02-01 11:41
edited on: 2010-02-01 11:42

1. This is something you should file a bug report against the package. not MPD. (IMHO). If we enable pipe output by default, because the packagers are incapable of passing the right configure flag, is doing it for the wrong reasons.
If your fridge breaks, you don't invent a weather control machine to keep your food cold...

2. if you compile mpd yourself, apt gives you then nice command apt-get build-dep mpd, this will install all dependencies needed to compile mpd as provided by ubuntu.
The fact you cannot find liblame/libwavpack is not relevant...

(0005315)
jeffayle (reporter)
2010-02-01 12:18

Is there a reason it should not be on by default? I don't compile very much software, but it seems to me everything should be on by default, unless there's a reason it shouldn't be.

I imagine the reason pipe output is off by default is that when it was added, it was still experimental/buggy, but it seems to me that it is stable now.

So, if there is still a valid reason it is not on by default (like known to cause problems with something else, et cetera), you can close the ticket, but if not, I don't see a reason why it should just not be on.

(0005316)
cirrus (administrator)
2010-02-01 12:31

It is off by default because it is a hack, which does not match our quality standards. If users think that it should be turned on by default, then why not, but I'm not comfortable with supporting this plugin.

(0005322)
jeffayle (reporter)
2010-02-02 12:18

Okay, that makes sense.

You can close this then.

(0005323)
Avuton Olrich (administrator)
2010-02-03 23:10

Your wish is my command.

Issue History
Date Modified	Username	Field	Change
2010-01-31 20:23	jeffayle	New Issue
2010-01-31 20:23	jeffayle	Status	new => assigned
2010-01-31 20:23	jeffayle	Assigned To	=> cirrus
2010-02-01 03:53	qball	Note Added: 0005310
2010-02-01 10:31	jeffayle	Note Added: 0005313
2010-02-01 11:41	qball	Note Added: 0005314
2010-02-01 11:42	qball	Note Edited: 0005314
2010-02-01 12:18	jeffayle	Note Added: 0005315
2010-02-01 12:31	cirrus	Note Added: 0005316
2010-02-02 12:18	jeffayle	Note Added: 0005322
2010-02-03 23:10	Avuton Olrich	Note Added: 0005323
2010-02-03 23:10	Avuton Olrich	Status	assigned => closed
2010-02-03 23:10	Avuton Olrich	Resolution	open => won't fix

Notes
(0005310) qball (administrator) 2010-02-01 03:53	Why? Motivation would be nice!!

(0005313) jeffayle (reporter) 2010-02-01 10:31	If you insist! (Not sure if I can edit this into the ticket) The reason I want pipe output enabled by default is so that it will make its way into distribution repositories like that. The other day, I downloaded the latest source so that I could compile it myself with pipe support, which didn't work out too well because I couldn't get Ubuntu to install liblame or libwavpack, so I only ad flac support. Now, the advantage of having pipe output would be that anyone could make a new output plugin, which would mean that MPD could do some really cool stuff. For example, the reason I went and compiled it myself was so that I could use a pipe output to stream to airtunes, which I got (somewhat) working in less than half an hour.

(0005314) qball (administrator) 2010-02-01 11:41 edited on: 2010-02-01 11:42	1. This is something you should file a bug report against the package. not MPD. (IMHO). If we enable pipe output by default, because the packagers are incapable of passing the right configure flag, is doing it for the wrong reasons. If your fridge breaks, you don't invent a weather control machine to keep your food cold... 2. if you compile mpd yourself, apt gives you then nice command apt-get build-dep mpd, this will install all dependencies needed to compile mpd as provided by ubuntu. The fact you cannot find liblame/libwavpack is not relevant...

(0005315) jeffayle (reporter) 2010-02-01 12:18	Is there a reason it should not be on by default? I don't compile very much software, but it seems to me everything should be on by default, unless there's a reason it shouldn't be. I imagine the reason pipe output is off by default is that when it was added, it was still experimental/buggy, but it seems to me that it is stable now. So, if there is still a valid reason it is not on by default (like known to cause problems with something else, et cetera), you can close the ticket, but if not, I don't see a reason why it should just not be on.

(0005316) cirrus (administrator) 2010-02-01 12:31	It is off by default because it is a hack, which does not match our quality standards. If users think that it should be turned on by default, then why not, but I'm not comfortable with supporting this plugin.

(0005322) jeffayle (reporter) 2010-02-02 12:18	Okay, that makes sense. You can close this then.

(0005323) Avuton Olrich (administrator) 2010-02-03 23:10	Your wish is my command.

Relationships