From: Sam Ravnborg <sam@ravnborg.org>
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 19:51:16 +0200 [thread overview]
Message-ID: <20070912175116.GB18311@uranus.ravnborg.org> (raw)
In-Reply-To: <1189617081.31502.78.camel@tara.firmix.at>
On Wed, Sep 12, 2007 at 07:11:21PM +0200, Bernd Petrovitsch wrote:
> On Wed, 2007-09-12 at 19:05 +0200, Sam Ravnborg wrote:
> [....]
> > Being rpm ignorant I do not know what the expected content of a kernel-source RPM
> > are but this is the available targets for kernel packaging (from make help):
>
> The kernel-source including all patches and configured as usually to be
> found under
> /usr/src/linux-$VERSION (or so). One needs that for e.g. external
> modules.
For external modules you need a fully build kernel which may be
clean up by "make clean".
Thats not the same as a source RPM as per my understanding.
Sam
next prev parent reply other threads:[~2007-09-12 17:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 16:13 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 [this message]
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 ` Jan Engelhardt
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
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=20070912175116.GB18311@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--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
all inboxes | Powered by JetHome®