From: Thorsten Leemhuis <fedora@leemhuis.info>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Bernd Petrovitsch <bernd@firmix.at>,
Dan Stromberg <dstromberglists@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Building a kernel-source RPM (not a kernel RPM)?
Date: Thu, 13 Sep 2007 19:26:31 +0200 [thread overview]
Message-ID: <46E972C7.7080004@leemhuis.info> (raw)
In-Reply-To: <20070913172210.GA26864@uranus.ravnborg.org>
On 13.09.2007 19:22, Sam Ravnborg wrote:
> On Thu, Sep 13, 2007 at 07:09:18PM +0200, Thorsten Leemhuis wrote:
>> On 12.09.2007 22:03, Sam Ravnborg wrote:
>>>> I think the Fedora approach has many benefits -- I always wondered why
>>>> it never went upstream like a "make install_develstuff" that install all
>>>> the needed bits to
>>>> /lib/modules/$(uname -r)/build/
>>> Last time I saw the patch is was to ugly to consider.
>> Do you have a pointer to that patch?
> See: http://lkml.org/lkml/2007/9/12/331
> Chris Wedgwood posted it today.
Missed that -- thx for the pointer and sorry for the noise.
Cu
knurd
next prev parent reply other threads:[~2007-09-13 17:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 16:13 Building a kernel-source RPM (not a kernel RPM)? Dan Stromberg
2007-09-12 16:49 ` Dan Stromberg
2007-09-12 17:05 ` Sam Ravnborg
2007-09-12 17:11 ` Bernd Petrovitsch
2007-09-12 17:51 ` Sam Ravnborg
2007-09-12 18:10 ` Bernd Petrovitsch
2007-09-12 18:16 ` Sam Ravnborg
2007-09-12 18:23 ` Bernd Petrovitsch
2007-09-12 20:23 ` Jan Engelhardt
2007-09-12 21:05 ` linux-os (Dick Johnson)
2007-09-12 17:09 ` Bernd Petrovitsch
2007-09-12 17:31 ` Dan Stromberg
2007-09-12 18:03 ` Bernd Petrovitsch
2007-09-12 19:46 ` Thorsten Leemhuis
2007-09-12 20:03 ` Sam Ravnborg
2007-09-13 17:09 ` Thorsten Leemhuis
2007-09-13 17:22 ` Sam Ravnborg
2007-09-13 17:26 ` Thorsten Leemhuis [this message]
2007-09-12 18:03 ` Jan Engelhardt
2007-09-13 16:09 ` Chuck Ebbert
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=46E972C7.7080004@leemhuis.info \
--to=fedora@leemhuis.info \
--cc=bernd@firmix.at \
--cc=dstromberglists@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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