public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: Susanne Oberhauser <froh@novell.com>,
	Jan Blunck <jblunck@suse.de>,
	Linux-Kernel Mailinglist <linux-kernel@vger.kernel.org>,
	opensuse-kernel@opensuse.org, opensuse@opensuse.org
Subject: Re: Testing the Current Upstream Kernel
Date: Fri, 17 Aug 2007 10:31:19 -0400	[thread overview]
Message-ID: <20070817143119.GB13008@redhat.com> (raw)
In-Reply-To: <6891.1187273061@turing-police.cc.vt.edu>

On Thu, Aug 16, 2007 at 10:04:21AM -0400, Valdis.Kletnieks@vt.edu wrote:
 > On Thu, 16 Aug 2007 12:28:34 +0200, Susanne Oberhauser said:
 > > Jan Blunck <jblunck@suse.de> writes:
 > > 
 > > > With our openSUSE Build Service we build a daily kernel, where we take
 > > > nightly snapshots of the current upstream development kernel (Linus' kernel
 > > > tree linux-2.6.git) without any patches (besides those we need for building a
 > > > RPM).  We do call this the vanilla kernel. It can be downloaded from:
 > > > 
 > > >  http://download.opensuse.org/repositories/Kernel:/Vanilla/SUSE_Factory/
 > > 
 > > Would it make sense to build it for the other distros as well?  like
 > > debian, fedora and mandrake?  I mena in _theory_ we could build it for
 > > those distros in the build server, couldn't we?
 > 
 > Most of the distros prefer a chance to add their own "Special Sauce" to it
 > before building, and building inside their build environment (for instance,
 > Fedora RPM's get PGP-signed - *that* would be a trust issue right there).
 > 
 > The current Fedora Rawhide kernel is 'kernel-2.6.23-0.105.rc3.fc8', and a few
 > RPMs ago it was based against -rc2-git5, so they track *very* close.  I think
 > that crew is managing well enough without help from the kernel.org build
 > server.

FWIW, you've been able to build the Fedora SRPMs with --with-vanilla
for a while now, which generates an RPM with no patches at all other
than the -rc/-git on which its based.
We're trying to work out logistics of which repository etc we're
going to host this in, but soon we'll be able to just offer
'yum install kernel-vanilla' to users.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-08-17 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s2ihcn1vwob.fsf@totally-fudged-out-message-id>
2007-08-16 10:28 ` Testing the Current Upstream Kernel Susanne Oberhauser
2007-08-16 14:04   ` Valdis.Kletnieks
2007-08-17 14:31     ` Dave Jones [this message]
2007-08-17 15:49       ` Dave Jones
2007-08-15 11:08 Jan Blunck
2007-08-15 11:14 ` Sam Ravnborg
2007-08-15 11:37   ` Jan Blunck

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=20070817143119.GB13008@redhat.com \
    --to=davej@redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=froh@novell.com \
    --cc=jblunck@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensuse-kernel@opensuse.org \
    --cc=opensuse@opensuse.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