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