public inbox for gentoo-kernel@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Mylchreest <johnm@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] kernel-2.eclass: Easier way to use genpatches in ebuilds
Date: Wed, 22 Jun 2005 17:24:50 +0100	[thread overview]
Message-ID: <1119457490.32703.77.camel@localhost> (raw)
In-Reply-To: <42B95F0D.1040408@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2430 bytes --]

This approach is fine with me, anything which makes life easier.
I have attached the kernel-2 from my overlay which as per bug #96510
If you agree with the idea, (its been tested) then please feel free to
merge and commit.

if you don't like the prerm stuff, just ditch it and apply to the
current stable.

Thanks for the work.
- John


On Wed, 2005-06-22 at 13:52 +0100, Daniel Drake wrote:
> This provides an easier way for kernel-2 users to apply genpatches.
> 
> In the attached ebuild example, ck-sources-2.6.12_p2.ebuild, all that is
> needed is:
> 
> K_WANT_GENPATCHES="base"
> K_GENPATCHES_VER="1"
> 
> The above will translate to genpatches-2.6.12-1.base.tar.bz2
> The only other thing you need to do is add $GENPATCHES_URI to SRC_URI and then
> you will get genpatches applied with unipatch.
> 
> Any comments?
> plain text document attachment (ck-sources-2.6.12_p2.ebuild)
> # Copyright 1999-2005 Gentoo Foundation
> # Distributed under the terms of the GNU General Public License v2
> # $Header: /var/cvsroot/gentoo-x86/sys-kernel/ck-sources/ck-sources-2.6.11_p10.ebuild,v 1.1 2005/06/13 02:07:56 marineam Exp $
> 
> K_PREPATCHED="yes"
> UNIPATCH_STRICTORDER="yes"
> K_NOUSENAME="yes"
> K_WANT_GENPATCHES="base"
> K_GENPATCHES_VER="1"
> ETYPE="sources"
> inherit kernel-2
> detect_version
> 
> # A few hacks to set ck version via _p instead of -r
> MY_P=${P/_p*/}
> MY_PR=${PR/r/-r}
> MY_PR=${MY_PR/-r0/}
> EXTRAVERSION=-ck${PV/*_p/}${MY_PR}
> KV_FULL=${OKV}${EXTRAVERSION}
> KV_CK=${KV_FULL/-r*/}
> detect_version
> 
> IUSE="ck-server"
> if use ck-server; then
> 	CK_PATCH="patch-${KV_CK}-server.bz2"
> else
> 	CK_PATCH="patch-${KV_CK}.bz2"
> fi
> 
> UNIPATCH_LIST="${DISTDIR}/${CK_PATCH}"
> 
> DESCRIPTION="Full sources for the Stock Linux kernel and Con Kolivas's high performance patchset"
> HOMEPAGE="http://members.optusnet.com.au/ckolivas/kernel/"
> SRC_URI="${KERNEL_URI} ${GENPATCHES_URI}
> 	ck-server? ( http://ck.kolivas.org/patches/2.6/${OKV}/${KV_CK}/patch-${KV_CK}-server.bz2 )
> 	!ck-server? ( http://ck.kolivas.org/patches/2.6/${OKV}/${KV_CK}/patch-${KV_CK}.bz2 )"
> 
> KEYWORDS="~x86 ~amd64"
> 
> pkg_postinst() {
> 	postinst_sources
> 
> 	einfo "The ck patchset is tuned for desktop usage."
> 	einfo "To better tune the kernel for server applications add"
> 	einfo "ck-server to your use flags and reemerge ck-sources"
> }
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-06-22 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22 12:52 [gentoo-kernel] kernel-2.eclass: Easier way to use genpatches in ebuilds Daniel Drake
2005-06-22 16:24 ` John Mylchreest [this message]
2005-06-23 19:36   ` John Mylchreest
2005-06-23  8:30 ` Henrik Brix Andersen
2005-07-01  9:08 ` Henrik Brix Andersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1119457490.32703.77.camel@localhost \
    --to=johnm@gentoo.org \
    --cc=gentoo-kernel@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox