| 1 |
On Mon, 2003-10-20 at 00:33, Kumba wrote: |
| 2 |
> Donnie Berkholz wrote: |
| 3 |
<snip> |
| 4 |
> > Currently I'm applying this patch if /usr/src/linux is linked to a 2.4 |
| 5 |
> > kernel at compile-time. |
| 6 |
<snip> |
| 7 |
> Here's an idea. Bit demented, though. |
| 8 |
> |
| 9 |
> First, why check /usr/src/linux? IMHO, that link may or may not always |
| 10 |
> be there or be correct. I recommend instead using the get_KV and |
| 11 |
> KV_to_int functions defined in /sbin/functions.sh to determine what the |
| 12 |
> machine is currently running. |
| 13 |
|
| 14 |
Because everything in Gentoo that needs a kernel should compile against |
| 15 |
/usr/src/linux. pcmcia-cs does so, xfree-drm does so, nvidia-kernel does |
| 16 |
so, ati-drivers does so ... |
| 17 |
|
| 18 |
> |
| 19 |
> The second part is where to apply the patch, and how. This is the |
| 20 |
> difficult part. I'd first say to apply it from the kernel.eclass file, |
| 21 |
> but this likely goes against some odd policy somewheres, which means |
| 22 |
> most modern 2.4 ebuilds would need updating to use this patch. Alot of |
| 23 |
> work is involved in tweaking all the 2.4 sources ebuilds. |
| 24 |
|
| 25 |
Hm, I think you may be misunderstanding here. The patch is against |
| 26 |
xfree, but based on which kernel is there, so applying from a kernel |
| 27 |
eclass doesn't really make sense. |
| 28 |
|
| 29 |
> |
| 30 |
> The third part is How to know when to apply the patch? In pseudo-codish |
| 31 |
> form, here is what I can come up with. |
| 32 |
<snip code on applying patch> |
| 33 |
> That should go into pkg_postinst, and probably include a sleep delay |
| 34 |
> timer + bell dinging like on portage and baselayout ebuilds to get the |
| 35 |
> attention of users. |
| 36 |
|
| 37 |
I've already got code prepared to take advantage of /usr/src/linux. |
Archives