from localhost (jalapeno [127.0.0.1])
	by jmason.org (Postfix) with ESMTP id 72F8016F03
	for <jm@localhost>; Wed,  2 Oct 2002 11:45:07 +0100 (IST)
from jalapeno [127.0.0.1]
	by localhost with IMAP (fetchmail-5.9.0)
	for jm@localhost (single-drop); Wed, 02 Oct 2002 11:45:07 +0100 (IST)
from egwn.net (ns2.egwn.net [193.172.5.4]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g929MRK02153 for
    <jm-rpm@jmason.org>; Wed, 2 Oct 2002 10:22:28 +0100
from evv.kamakiriad.local (cable-b-36.sigecom.net
    [63.69.210.36]) by egwn.net (8.11.6/8.11.6/EGWN) with ESMTP id
    g929JBf01178 for <rpm-list@freshrpms.net>; Wed, 2 Oct 2002 11:19:11 +0200
from aquila.kamakiriad.local (aquila.kamakiriad.local
    [192.168.1.3]) by kamakiriad.comamakiriad.com (8.11.6/8.11.6) with SMTP id
    g929J2M08406 for <rpm-list@freshrpms.net>; Wed, 2 Oct 2002 04:19:02 -0500
From rpm-list-admin@freshrpms.net  Wed Oct  2 11:45:08 2002

from lugh.tuatha.org (root@lugh.tuatha.org [194.125.145.45]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g82Am8Z29220 for
    <zzzz-ilug@example.com>; Mon, 2 Sep 2002 11:48:08 +0100

from localhost (jalapeno [127.0.0.1])
	by jmason.org (Postfix) with ESMTP id 246BD16F16
	for <jm@localhost>; Thu,  3 Oct 2002 12:21:41 +0100 (IST)
from jalapeno [127.0.0.1]
	by localhost with IMAP (fetchmail-5.9.0)
	for jm@localhost (single-drop); Thu, 03 Oct 2002 12:21:41 +0100 (IST)
from egwn.net (ns2.egwn.net [193.172.5.4]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g92KotK28220 for
    <jm-rpm@jmason.org>; Wed, 2 Oct 2002 21:50:55 +0100
from python (80-24-132-206.uc.nombres.ttd.es [80.24.132.206])
    (authenticated) by egwn.net (8.11.6/8.11.6/EGWN) with ESMTP id
    g92KjBf05505 for <rpm-list@freshrpms.net>; Wed, 2 Oct 2002 22:45:12 +0200
From rpm-list-admin@freshrpms.net  Thu Oct  3 12:21:41 2002

Once upon a time, Gary wrote :
> On Wed, Oct 02, 2002 at 10:09:19AM +0200, Matthias Saou wrote:
> > Well, I don't really find it consistent at all to use an rpm package
> > built against something that wasn't installed through rpm :-/
>
> Following that reasoning, I've been installing all my custom-built
> kernels through rpm recently. I find it annoying, though, that
> alsa-kernel, and similar packages, will only build for the currently
> running kernel.
>
> So I've attached a patch to specify an alternate kernel by setting the
> "TARGET_KERNEL" environment variable before running rpmbuild. You
> still need to have the rpm for the specified kernel installed, but at
> least it doesn't have to be currently running. It's kinda hackish, so
> if someone has a better way to do this, let me know.
That idea looks good although it maybe needs to be tweaked a bit more (what
you sent doesn't support packages named "kernel-smp"). I'd also prefer a
cleaner way than the env variable, and preferrably not editing the spec...
probably "--define 'target 2.4.xx-xx' --with smp". Sound good enough?
The BuildRequires on "kernel-source" will also need to be removed because
it won't necessarily need to be true, and that does bug me a bit :-/
More ideas are welcome.
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Red Hat Linux release 7.3 (Valhalla) running Linux kernel 2.4.18-10acpi
Load : 0.08 0.06 0.03
_______________________________________________
RPM-List mailing list <RPM-List@freshrpms.net>
http://lists.freshrpms.net/mailman/listinfo/rpm-list