From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13997 invoked by uid 1002); 20 Oct 2003 05:00:00 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 21376 invoked from network); 20 Oct 2003 05:00:00 -0000 From: Donnie Berkholz To: gentoo-dev@gentoo.org In-Reply-To: <3F9365A5.5000509@gentoo.org> References: <1066617251.991.5.camel@sfa237013.richmond.edu> <3F9365A5.5000509@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-hv4bXwpUXV/jGQruGlz+" Message-Id: <1066625988.5592.31.camel@sfa237013.richmond.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 20 Oct 2003 00:59:48 -0400 X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-39, required 5, EMAIL_ATTRIBUTION, IN_REP_TO, MIME_LONG_LINE_QP, PGP_SIGNATURE_2, QUOTED_EMAIL_TEXT, QUOTE_TWICE_1, REFERENCES, REPLY_WITH_QUOTES, USER_AGENT_XIMIAN) Subject: Re: [gentoo-dev] Patches and the 2.4->2.6 move X-Archives-Salt: 43ca6d21-aa23-4e23-a0e2-5d81768034ae X-Archives-Hash: b3d1187ab75fc6a65a8552fd91d8b714 --=-hv4bXwpUXV/jGQruGlz+ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2003-10-20 at 00:33, Kumba wrote: > Donnie Berkholz wrote: > > Currently I'm applying this patch if /usr/src/linux is linked to a 2.4 > > kernel at compile-time. > Here's an idea. Bit demented, though. >=20 > First, why check /usr/src/linux? IMHO, that link may or may not always=20 > be there or be correct. I recommend instead using the get_KV and=20 > KV_to_int functions defined in /sbin/functions.sh to determine what the=20 > 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 ... >=20 > 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,=20 > but this likely goes against some odd policy somewheres, which means=20 > most modern 2.4 ebuilds would need updating to use this patch. Alot of=20 > 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. >=20 > The third part is How to know when to apply the patch? In pseudo-codish=20 > form, here is what I can come up with. > That should go into pkg_postinst, and probably include a sleep delay=20 > timer + bell dinging like on portage and baselayout ebuilds to get the=20 > attention of users. I've already got code prepared to take advantage of /usr/src/linux. --=-hv4bXwpUXV/jGQruGlz+ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQA/k2vEXVaO67S1rtsRAmqzAKCSlEyKyUCZxlrbWQlqqeXHWN2xGQCeLfwb PNsbN4JbIoT4zKsL/q2Xh3Q= =+gTD -----END PGP SIGNATURE----- --=-hv4bXwpUXV/jGQruGlz+--