public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <fedora@leemhuis.info>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: Dan Stromberg <dstromberglists@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Building a kernel-source RPM (not a kernel RPM)?
Date: Wed, 12 Sep 2007 21:46:16 +0200	[thread overview]
Message-ID: <46E84208.1050903@leemhuis.info> (raw)
In-Reply-To: <1189620186.31502.96.camel@tara.firmix.at>

On 12.09.2007 20:03, Bernd Petrovitsch wrote:
> On Wed, 2007-09-12 at 10:31 -0700, Dan Stromberg wrote:
>> On Wed, 12 Sep 2007 19:09:26 +0200, Bernd Petrovitsch wrote:
> [...]
>>> Fedora BTW abandoned kernel-source* and they have now a website with a
>>> description
>>> how to produce a configured kernel source tree (e.g. for out-of-tree
>>> modules).

That explanation is IMHO a bit misleading. Fedora ships kernel-devel
packages for all their kernels. Those contain everything from the
source-tree that's needed to build out-of-tree modules -- Makefiles for
example, but no real sources.

Well, to be more precise: that is enought for out-of-tree modules that
get shipped with proper Makefiles/Layout, which is the case for nearly
every external module these days. The "website with a description how to
produce a configured kernel source tree" exists as well, for people that
want to build kernels the way the Fedora builds them, but want to apply
additional patches/other sources.

>> So this is as smooth as producing kernel-source RPM's gets?
> I had no problems with the kernel-source.*.rpm approach.

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/

CU
knurd



  reply	other threads:[~2007-09-12 19:46 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 [this message]
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
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=46E84208.1050903@leemhuis.info \
    --to=fedora@leemhuis.info \
    --cc=bernd@firmix.at \
    --cc=dstromberglists@gmail.com \
    --cc=linux-kernel@vger.kernel.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