1 |
Andrew Gaffney wrote: |
2 |
> A. Khattri wrote: |
3 |
>> I have no problem with change as long as there is an easy way to keep |
4 |
>> what |
5 |
>> we have. After all, Gentoo is about having a choice and removing the |
6 |
>> apache flag from PHP without providing some other mechanism to keep it is |
7 |
>> simply removing choice. |
8 |
> |
9 |
> I see this type of argument used all the time. Some people just don't |
10 |
> seem to get the fact that all Gentoo devs are volunteers, and we will do |
11 |
> whatever makes it easier on *us*. If you don't like it, don't bitch |
12 |
> about choice. You have the *choice* to learn how to maintain the stuff |
13 |
> yourself and not complain. You don't pay for Gentoo, so you don't have |
14 |
> the right to tell any Gentoo dev what to do with their volunteer |
15 |
> time.</rant> |
16 |
|
17 |
If people are using this argument all the time, it might be |
18 |
worth considering why they are. |
19 |
|
20 |
Gentoo tends to remove packages or change them in a way that |
21 |
is not rearward-compatible more readily than other distributions. |
22 |
I understand that the labor is all volunteer, however, other, |
23 |
more stable/mature distributions are also all-volunteer, but yes, |
24 |
that's the way it is. People spend their volunteer time as they |
25 |
see fit, I understand this completely. |
26 |
|
27 |
The result, however, is that Gentoo becomes an inappropriate |
28 |
choice for a production server deployment. I haven't suggested |
29 |
Gentoo for production servers to anyone (especially my employers) |
30 |
since somewhere around 2003 for this reason. |
31 |
|
32 |
At work, my team of a few dozen people support tens of thousands |
33 |
of Linux servers. We wrote our own tools for installation, |
34 |
distribution, and maintenance of OSes and package sets. There was |
35 |
a time when I considered that we could use Gentoo. Our own custom |
36 |
Portage repositories could be maintained, and the portage tools |
37 |
would cover a lot of the things we need to do very nicely. It'd |
38 |
be great to build on the work of other Gentoo contributors, and |
39 |
we'd no doubt join the larger community of contributors. But I |
40 |
simply can't recommend this. The Gentoo developers and packagers |
41 |
in general seem more interested in the latest shiny thing rather |
42 |
than stability, reliability, and predictability. Fine for a desktop, |
43 |
but antithetical to the needs of people running mission-critical |
44 |
server farms. As you point out, it's entirely the prerogative of |
45 |
the developers and packagers to set their own priorities, and I |
46 |
agree of course, but do be aware of the results of the choices of |
47 |
Gentoo packagers and developers and how they collectively create |
48 |
the personality of the distro and how that personality effects the |
49 |
choices of other potential contributors and users of Gentoo Linux. |
50 |
|
51 |
-Mark (who uses Gentoo on his personal systems these days) |
52 |
-- |
53 |
gentoo-server@g.o mailing list |