1 |
'afternoon, Canek! |
2 |
|
3 |
On Fri, Apr 26, 2013 at 12:02:38PM -0500, Canek Peláez Valdés wrote: |
4 |
> On Fri, Apr 26, 2013 at 11:29 AM, Alan Mackenzie <acm@×××.de> wrote: |
5 |
> [snip] |
6 |
> > Somebody reported that pulseaudio is an absolute requirement for Gnome |
7 |
> >>=3.8. That may not be 100% of users, but the "forced" is certainly |
8 |
> > there. |
9 |
|
10 |
> No one is forcing nothing on anyone, since nobody is forcing no one to |
11 |
> use GNOME, Gentoo, or Linux for that matter. |
12 |
|
13 |
That's a strawman argument. Anytime a free software project drops |
14 |
support for something, it forces its users to make choices. Yes, force. |
15 |
|
16 |
> The developers of any project can always decide the dependencies of a |
17 |
> project. If you are not a developer, you simply have no vote in the |
18 |
> matter, although you certainly always have voice... that they can |
19 |
> choose to ignore. |
20 |
|
21 |
Free software developers, having got people to commit to using their |
22 |
software, have responsibilities, albeit moral ones. The prime one is to |
23 |
support their users. You'll surely have noticed that what gets up the |
24 |
noses of people on this mailing list most is when support for reasonable |
25 |
configurations gets dropped. Witness all the recent trouble over eth0, |
26 |
for example. |
27 |
|
28 |
> > There's a difference between a "default choice" and an absolute |
29 |
> > requirement. |
30 |
|
31 |
> Yeah; and the decision is for the developers to make. |
32 |
|
33 |
> >> Basically there's a bunch of vague criticisms of unnamed systems where |
34 |
> >> "they" force stuff on "all users" for "no good reason". Nevermind that |
35 |
> >> we can actually state what the reasons are. Fingers in the ears. |
36 |
> >> neener neener. |
37 |
|
38 |
> > Please feel free to state those reasons, which as far as I can see, |
39 |
> > nobody has done yet in this thread; "they" being the gnome team, and the |
40 |
> > reasons being for the forcing, not for a non-existent "default choice". |
41 |
|
42 |
> If GNOME has to support PA and non-pa systems, they need to code, |
43 |
> test, support and bug-fix 2 different sets of of systems. If they need |
44 |
> to support ConsoleKit and logind, the number grows to 4 (PA/ck, |
45 |
> PA/logind, non-PA/ck, non-PA/logind). With 3 different optional |
46 |
> requirements, it's 8 sets of systems. With 4, is 16. With n, it's 2^n. |
47 |
|
48 |
> That's exponential growth, which in CS is always no-no. |
49 |
|
50 |
WADR, that is simply false. With features which interact chaotically |
51 |
with eachother, yes, you have exponential growth. With distinct, |
52 |
self-contained features, each one is merely an incremental test effort. |
53 |
ALSA and pulseaudio are self-contained, and are also well tested in their |
54 |
own right. Only integration needs testing. |
55 |
|
56 |
If you were serious about this exponential growth, how on earth could, |
57 |
e.g., the Linux kernel or Emacs, both with thousands of options[*], |
58 |
possibly get tested anywhere near acceptably? |
59 |
|
60 |
[*] 12,666 in Linux 3.7.10, 7,510 in vanilla Emacs 24.3. |
61 |
|
62 |
> Who is going to code, test, support and bug fix all those possible |
63 |
> configurations? You? |
64 |
|
65 |
No. The gnome developers. I test and support all reasonable (and many |
66 |
unreasonable) combinations on my own free software project. |
67 |
|
68 |
> The GNOME developers simply cannot support all different sets of |
69 |
> possible configurations, and PA covers the sound needs of *ALL* users |
70 |
> (doesn't matter if you like it or not), even the simple cases. |
71 |
|
72 |
What about the needs of those high-end audio users, for example, who need |
73 |
jack? |
74 |
|
75 |
What about those, like me, with audio problems, where the need exists to |
76 |
strip a system down so as to isolate those problems? |
77 |
|
78 |
> If PA has bugs in some configuration, those bugs need to be fixed; the |
79 |
> solution (in the GNOME developers view) is not to "remove PA", since |
80 |
> the goal of the project is to cover *ALL* use cases. |
81 |
|
82 |
pulseaudio is a server component - gnome is an application. They are at |
83 |
different levels of the system hierarchy, just as a mail transport agent |
84 |
and mail user agent are. The maintainers of mutt don't force the use of, |
85 |
say, postfix. By long tradition on *nix, sysadmins configure their own |
86 |
systems, selecting those components which best fit their needs. gnome's |
87 |
decision to mandate pulseaudio interferes with this tradition. IMAO, |
88 |
this is a Bad Thing. |
89 |
|
90 |
> But hey, the source is there; feel free to patch whatever needs to be |
91 |
> patched in GNOME (and probably GStreamer) so it doesn't require PA. |
92 |
> Just be certain that those patches will be rejected by upstream, for |
93 |
> the reasons stated above. |
94 |
|
95 |
Making minor changes to free software is impracticable on a casual basis. |
96 |
Only forking a project can do this. You know this full well. |
97 |
|
98 |
> And by the way, this is also true for Gentoo: it cannot support all |
99 |
> different sets of possible configurations, no matter how hard they/we |
100 |
> try. |
101 |
|
102 |
It come pretty close. :-) |
103 |
|
104 |
> Regards. |
105 |
> -- |
106 |
> Canek Peláez Valdés |
107 |
|
108 |
-- |
109 |
Alan Mackenzie (Nuremberg, Germany). |