Re: [gentoo-user] linux boot logo in 2.6.29-gentoo sources

[Eric Martin]

Jorge Morais wrote:
> On Fri, 27 Mar 2009 03:36:41 +0500
> Mike Kazantsev <mike_kazantsev@×××××××.net> wrote:
>
>> On Thu, 26 Mar 2009 19:13:38 -0300
>> Jorge Morais <please.no.spam.here@×××××.com> wrote:
>>
>>> If you had upgraded because of a needed feature, I assume you would
>>> have read about the release, and thus would know about Tuz.
>>> So you upgraded to a ~arch kernel without any need.
>>> Why?
>> The question is probably not adressed to me, but...
>>
>> It's still a way to check out these new features hands-on :)
> It's a kernel.
>> And while it's ~arch on gentoo, it's actually marked 'stable' by
>> developers, and, since gentoo ebuild does pretty much nothing but
>> unpacking it, it should be pretty much as stable as any non-~arch
>> package.
>>
>
> Even if it already released, it has a higher chance of bugs than a
> more established kernel.
>
> Waiting for the package to become stable on Gentoo is not just about
> ebuild bugs; it is also about waiting for enough users in general to
> test the upstream package, and Gentoo users in particular to test the
> package within Gentoo.
>
> And I don't know about the usual quality of brand new Linux
> releases, but in general, I believe upstream developers want to
> release early (to get testers and updated contributions), while
> a distribution may wait until the software is ready and tested.
>

> Cheers,
>     Jorge
>

I personally do it to get all of the code updates.  all of my boxes are
on ~arch for gentoo-sources / hardened-sources and I haven't had 1
problem yet.  Also, the kernel is the last place that you want to drag
your feet for updates.  If there's a bug in the kernel I want to have it
fixed asap.  Granted you can also argue that I'm injecting buggy code.
It's two sides of the same coin.

-- 
Eric Martin
Key fingerprint = D1C4 086E DBB5 C18E 6FDA  B215 6A25 7174 A941 3B9F