public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: linux-kernel@vger.kernel.org
Subject: Re: kbuild make deb patch
Date: Sun, 13 Jun 2004 08:19:57 +0200	[thread overview]
Message-ID: <20040613061957.GA3012@mars.ravnborg.org> (raw)
In-Reply-To: <20040609142141.GT20632@lug-owl.de>

On Wed, Jun 09, 2004 at 04:21:41PM +0200, Jan-Benedict Glaw wrote:
> On Tue, 2004-06-08 23:08:46 +0200, Sam Ravnborg <sam@ravnborg.org>
> wrote in message <20040608210846.GA5216@mars.ravnborg.org>:
> > On Mon, Jun 07, 2004 at 04:13:53PM +0200, Wichert Akkerman wrote:
> > I'm in progress of doing some infrastructure work to better support building
> > different packages. I have requests for .tar.gz, tar.gz2 as well
> > as deb.
> 
> (Being a Debian user...) I really *love* to see a .tar.{gz,bz2} target.
> For my in-house use (as well in in the company I work for) we do have a
> script to basically install modules (+ vmlinuz + vmlinux + .config +
> System.map), adding some identifier to the filenames (of the last four
> files mentioned) and preparing a .tar.gz from that.

Could you try to be more specific in what you expect to see in a .tar.gz'ed kernel.
A script that creates a .tar.gz from current kernel would be fine :-)


I expect something like:
All files stored in a directory named: kernel-2.6.6-rc4/
Includes all source files
Includes .config

Do you expect to see a fully build kernel?
- With all .o files
- With the output file (bzImage or whatever used by selected architecture)

Anything else?

	Sam

  reply	other threads:[~2004-06-13  6:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 14:13 kbuild make deb patch Wichert Akkerman
2004-06-07 14:36 ` David Vrabel
2004-06-07 14:39   ` Wichert Akkerman
2004-06-07 15:13 ` Flavio Stanchina
2004-06-07 15:20   ` Wichert Akkerman
2004-06-08 21:08 ` Sam Ravnborg
2004-06-09 14:21   ` Jan-Benedict Glaw
2004-06-13  6:19     ` Sam Ravnborg [this message]
2004-06-14  8:30       ` Jan-Benedict Glaw

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=20040613061957.GA3012@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --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