| 1 |
Hi, |
| 2 |
|
| 3 |
On Fri, 2004-10-29 at 17:36, Peter Johanson wrote: |
| 4 |
> The goal of kernel-mod eclass is to enable kernel module ebuilds to have |
| 5 |
> an easier time doing what they do. If non-kernel module ebuilds are |
| 6 |
> using kernel-mod, we should investigate what functionality *those* |
| 7 |
> ebuilds use, and move that into a seperate eclass that kernel-mod.eclass |
| 8 |
> can then inherit from. Things like the kernel version variable |
| 9 |
> detection, etc, is what i'm guessing is used by other ebuilds (i don't |
| 10 |
> have time to dig currently) and we could certainly move that into |
| 11 |
> kernel-info.eclass or somesuch, and let kernel-mod.eclass inherit that. |
| 12 |
> Then we are free to do things like brix suggests, without annoying those |
| 13 |
> few ebuilds that think they are kernel module ebuilds, but are really |
| 14 |
> imposters. (: |
| 15 |
> |
| 16 |
> Comments? |
| 17 |
|
| 18 |
Sounds reasonable to me. The kernel-mod.eclass is intended for kernel |
| 19 |
modules, as you say. |
| 20 |
|
| 21 |
./Brix |
| 22 |
-- |
| 23 |
Henrik Brix Andersen <brix@g.o> |
| 24 |
Gentoo Linux |
Archives