| 1 |
On Mon, 2005-08-15 at 09:28 +0100, Neil Bothwick wrote: |
| 2 |
> I think some of this confusion is caused by the way people switch |
| 3 |
> between |
| 4 |
> two uses of the word stable. It can mean "doesn't crash", but then |
| 5 |
> most |
| 6 |
> upstream latest packages fit there, and some long standing releases |
| 7 |
> don't. It can also mean "not changing" and this is what some people |
| 8 |
> want |
| 9 |
> from a distribution. |
| 10 |
|
| 11 |
I think there is a third meaning with gentoo, namely when the ebuild is |
| 12 |
working well enough - this is independent of whether the upstream |
| 13 |
package is stable.(although it no doubt helps if it is). So you can have |
| 14 |
kde make a release (stable in their view) but gentoo takes some |
| 15 |
considerable time to make ebuilds that work acceptably, before they are |
| 16 |
marked stable (eg x86 cf ~x86) |
| 17 |
|
| 18 |
|
| 19 |
> If you run a server farm, you don't want to be |
| 20 |
> continually upgrading just to get new features you don't need, you |
| 21 |
> just |
| 22 |
> want a system that works with timely security fixes. |
| 23 |
|
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Nick Rout <nick@×××××××.nz> |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-user@g.o mailing list |
Archives