| 1 |
On Wed, Aug 21, 2013 at 4:39 AM, Tom Wijsman <TomWij@g.o> wrote: |
| 2 |
> |
| 3 |
> "The latest distros seemed to be just a bunch of same old stuff. |
| 4 |
> Nothing new -- nothing innovative." ~ Larry's frustration. :( |
| 5 |
> |
| 6 |
> "Then Larry tried Gentoo Linux. He was just impressed. ... He |
| 7 |
> discovered lots of up-to-date packages ..." ~ Larry's happiness. :) |
| 8 |
> |
| 9 |
|
| 10 |
I'm not suggesting that we should be backporting bugfixes for two |
| 11 |
years. I'm just suggesting that it isn't a big deal if stable |
| 12 |
packages are ~90 days behind in general. Plus, Larry can always run |
| 13 |
the just-released KDE or whatever by accepting ~arch for that package |
| 14 |
and get a system where nothing other than KDE is likely to break. |
| 15 |
|
| 16 |
I have nothing against improvements that help us keep up though. If a |
| 17 |
package gets held up because of actual regressions (go read Ago's blog |
| 18 |
RE definition of a regression) that is one thing. If things get held |
| 19 |
up simply because nobody notices they're late, that is another. |
| 20 |
|
| 21 |
Plus, the innovation Larry was talking about doesn't mean having |
| 22 |
chrome-29 in the tree two days sooner than some other distro. What is |
| 23 |
innovative about Gentoo at its heart is letting the user have his cake |
| 24 |
and eat it too, like running a stable system but still getting |
| 25 |
chrome-29 near release day. I do firmly believe that Gentoo is a |
| 26 |
great distro for getting neat things done. |
| 27 |
|
| 28 |
Manpower will still always be an issue. I requested stable on mythtv |
| 29 |
on x86 a few weeks ago, but I can completely understand that |
| 30 |
client-server apps that typically involve hardware just aren't going |
| 31 |
to get turned around on a dime (FYI - if anybody wants to volunteer |
| 32 |
test that on x86 feel free to contact me and we can probably work |
| 33 |
something out with the x86 arch team together). |
| 34 |
|
| 35 |
Rich |
Archives