| 1 |
On Tue, 13 Jun 2006 19:54:47 +0200, Henrik Brix Andersen wrote: |
| 2 |
|
| 3 |
> On Tue, Jun 13, 2006 at 01:29:55PM -0400, Peter wrote: [snip] |
| 4 |
>> This kernel source will not cause Armageddon to arrive, cause smoke to |
| 5 |
>> issue from your power supply, nor interfere with other ebuilds. |
| 6 |
> |
| 7 |
> That's funny. Did you just claim that a sys-kernel/*-sources ebuild with |
| 8 |
> the patch-sets listed below would have no possibility of interfering with |
| 9 |
> other ebuilds? If so, you've just proven my point that many users wont be |
| 10 |
> able to judge how ebuilds from overlays may affect the stable tree. |
| 11 |
> |
| 12 |
|
| 13 |
I did. Sources don't affect anything. The ck-sources are in the tree, and |
| 14 |
there is dire warning associated with them. Only the -mm sources have any |
| 15 |
sort of warning. If a user CHOOSES to use a hacked up kernel, then they |
| 16 |
obviously choose to. Just like, if a user chooses to try out reiserfs-4, |
| 17 |
they get what they pay for. Sources don't affect anything. |
| 18 |
|
| 19 |
|
| 20 |
> "Features |
| 21 |
> -ck(s) Con Kolivas Patchset, (server version available as option) -ide |
| 22 |
> libATA/ide updates, Alsa updates and fixes, Dothan Speedstep, Pentium M |
| 23 |
> undervolt, IBM ACPI fan control, Suspend2, vesafb-tng, reiser4, unionfs |
| 24 |
> squashfs, realtime-lsm, fbsplash, configurable mouse polling support, |
| 25 |
> custom dsdt, Layer7, various fixes and updates." [1] |
| 26 |
> |
| 27 |
>> Am I being to simplistic or naive? |
| 28 |
> |
| 29 |
> Both, it seems. |
| 30 |
> |
| 31 |
> Regards, |
| 32 |
> Brix |
| 33 |
> |
| 34 |
> [1]: http://bugs.gentoo.org/show_bug.cgi?id=103354#c51 |
| 35 |
|
| 36 |
And I think these are worthwhile features. Some, actually are part of the |
| 37 |
gentoo-base and gentoo-extra patches (see the excludes list). It also |
| 38 |
includes spocks vesa-tng and fbsplash. |
| 39 |
|
| 40 |
Look, you can't micro-control all aspects of a user's computing |
| 41 |
experience. If someone downloads tmpwatch and mistakenly puts / in the |
| 42 |
list of directories to prune, what will you do? Put tmpwatch into |
| 43 |
package.mask because it MIGHT be misued? Or, will you package.mask |
| 44 |
vixie.cron because someone may not be capable of writing a bash script? |
| 45 |
|
| 46 |
Honestly, I do not see the difference, AND because the kernel is |
| 47 |
experimental (or, at least I call it experimental), and widely followed, I |
| 48 |
think Sunrise is ideal for it. JM2C. |
| 49 |
|
| 50 |
-- |
| 51 |
Peter |
| 52 |
|
| 53 |
|
| 54 |
-- |
| 55 |
gentoo-dev@g.o mailing list |
Archives