From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1J7zZB-0001qZ-M4 for garchives@archives.gentoo.org; Thu, 27 Dec 2007 20:42:58 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lBRKg3cd001530; Thu, 27 Dec 2007 20:42:03 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id lBRKg2Kv001525 for ; Thu, 27 Dec 2007 20:42:02 GMT Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 2BE96659DE for ; Thu, 27 Dec 2007 20:42:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: 0.694 X-Spam-Level: X-Spam-Status: No, score=0.694 required=5.5 tests=[AWL=0.714, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zfe30VYuu70T for ; Thu, 27 Dec 2007 20:41:56 +0000 (UTC) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.238]) by smtp.gentoo.org (Postfix) with ESMTP id 4B75B65729 for ; Thu, 27 Dec 2007 20:41:56 +0000 (UTC) Received: by nz-out-0506.google.com with SMTP id i1so657822nzh.39 for ; Thu, 27 Dec 2007 12:41:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:sender; bh=mrvZTrfP4hRhhvEKDQQSBlkbV4duts/7ZNLHR5T69hY=; b=HSvAtZO8l74Jtdf7r2mU75ftvPKccW1UlXw1Gbv6zSPzc8SAQPLXUTts1/QB/Nkdh2H4mVR3PZHhiAgsFQHff3RGV23/uY8jnz2uAFX2EVDOowx64HSPQ0GJZq9RJaFGnaLWpb1KVyTu2089eVwmU7xjF0pxXGfHlq3OzQpdjYY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer:sender; b=WOWrWzPT3h4vQsK+9DEMeVLDTF3u0LIGlX+BmLkb0nhFd9EbALs/EmtzbCxhS01k9Ja4vKUuJYQ4qkv9klWfsme+a4wXdaSpB4kw6NkzCxuhTYPYwFiuhH1MHZYK+1UFYY3U47boK2TAV7o4qj9pIXzTxsRxkS0MtV/veL7EyNs= Received: by 10.142.194.1 with SMTP id r1mr368725wff.176.1198788114985; Thu, 27 Dec 2007 12:41:54 -0800 (PST) Received: from ?192.168.1.33? ( [77.246.104.171]) by mx.google.com with ESMTPS id e23sm30804198ugd.56.2007.12.27.12.41.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 27 Dec 2007 12:41:54 -0800 (PST) Subject: [gentoo-kernel] Kernel patching solution. From: Peter Volkov To: gentoo-kernel@lists.gentoo.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-LI4/OEmonDCCkXDkgb3j" Date: Thu, 27 Dec 2007 23:39:54 +0300 Message-Id: <1198787994.2899.25.camel@localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-kernel@gentoo.org Reply-to: gentoo-kernel@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.12.2 Sender: Peter Volkov X-Archives-Salt: a32e619b-1286-4eea-826a-879aaa517e3b X-Archives-Hash: c26035bda0aee7f712adcafa6f967e94 --=-LI4/OEmonDCCkXDkgb3j Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hello, list. I just took maintenance of some ebuilds which require user to patch kernel, e.g. l7-filter. Actually l7-filter is the ebuild which only task is to patch kernel and I really hate the way it works: * it requires FEATURES=3D"-sandbox" * you have to reemerge l7-filter after each kernel update * and other similar problems the root of which is that portage never knows a kernel version the patch was already applied to. So I'm thinking on solution to fix this problem. First I've tried to rewrite ebuild to avoid FEATURES=3D"-sandbox" and this is possible, but does not fix other problems. The best idea I could think of to the moment is similar to webapps. emerge just installs patches to some known location while actual patching will be done with some external utility - kernel-patcher. Together with patching it will populate database with information about patches to which kernels were installed. So if user decides to find out what patches were installed to the kernel kernel-patcher will list that. Also if user decides to upgrade kernel it'll be possible to call kernel-patcher and suggest user to install patches, applied to currently symlinked (/usr/src/linux) kernel too, thus simplifying kernel upgrade. Well, I did not wrote all details I have in my head now, but before I've started to work on/draft this this I wanted to hear some opinions as I'm sure some of you already have thoughts about this. Is this feasible solution? Are there better? --=20 Peter. --=-LI4/OEmonDCCkXDkgb3j Content-Type: application/pgp-signature; name=signature.asc Content-Description: =?UTF-8?Q?=D0=AD=D1=82=D0=B0?= =?UTF-8?Q?_=D1=87=D0=B0=D1=81=D1=82=D1=8C?= =?UTF-8?Q?_=D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D1=8F?= =?UTF-8?Q?_=D0=BF=D0=BE=D0=B4=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=B0?= =?UTF-8?Q?_=D1=86=D0=B8=D1=84=D1=80=D0=BE=D0=B2=D0=BE=D0=B9?= =?UTF-8?Q?_=D0=BF=D0=BE=D0=B4=D0=BF=D0=B8=D1=81=D1=8C=D1=8E?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQBHdA2az6tlgEWSarMRAuAMAKCf+88MFhF3P2ZZE6gi5G753tuYJwCeO+jE y5sNwuzaKOId45ow8+t3ix8= =VNJf -----END PGP SIGNATURE----- --=-LI4/OEmonDCCkXDkgb3j-- -- gentoo-kernel@gentoo.org mailing list