1 |
On 6/13/06, Peter <pete4abw@×××××××.net> wrote: |
2 |
> As an example, there is a kernel source build I've been playing with. I |
3 |
> know, from the kernel team, it will never, repeat NEVER, get onto the |
4 |
> portage tree. they want no part of it. |
5 |
|
6 |
My guess is that alternative kernels are probably the strongest |
7 |
argument there is _in favor_ of having a user-supported overlay area. |
8 |
It represents very little risk of wasting developers time on chasing |
9 |
down false bug reports, since the kernel version shows up in the |
10 |
emerge --info output. Any bug report from a user running an |
11 |
unsupported (whether in-tree or out-of-tree) kernel can simply be |
12 |
closed with a "try again with a supported kernel, reopen if |
13 |
necessary". |
14 |
|
15 |
It does risk some extra iterations of problem solving on -user, since |
16 |
we don't have a policy of requiring everybody posting a question to |
17 |
supply their --info. But I think that would be acceptable. |
18 |
|
19 |
But this is a very specific case, and if it really needs to be on |
20 |
*.gentoo.org, it could be handled with a "ricer-kernels.o.g.o" |
21 |
overlay. I don't see any great reason why such an overlay would need |
22 |
to be hosted on o.g.o however. |
23 |
|
24 |
And this single case doesn't serve as an adequate counter-argument to |
25 |
the concerns about the broad scope of sunrise. |
26 |
|
27 |
> |
28 |
> This kernel source will not cause Armageddon to arrive, cause smoke to |
29 |
> issue from your power supply, nor interfere with other ebuilds. |
30 |
> |
31 |
|
32 |
So I take this to mean you are supplying a warranty for this kernel? |
33 |
Because AFAIK even the people who *wrote* the kernel are quite |
34 |
explicit in the "no warranty" provisions of the license. Not even if |
35 |
it spins your hard drive backwards causing your entire mp3 collection |
36 |
to be converted to Britney Spears songs! |
37 |
|
38 |
-Richard |
39 |
-- |
40 |
gentoo-dev@g.o mailing list |