Re: Packaging RC and -git releases

["Josh Boyer" <jwboyer@xxxxxxxxx>]

On 1/10/07, Greg KH <greg@xxxxxxxxx> wrote:
> On Wed, Jan 10, 2007 at 09:20:41AM -0600, Josh Boyer wrote:
> > Hi All,
> >
> > I'm curious as to how folks here package up RC and -git releases
> > across the various distros.  For example, Fedora currently packages
> > 2.6.20-rc4 as kernel-2.6.19-1.2906.fc7 given that it's still based on
> > the 2.6.19 tarball and applies the 2.6.20-rc4 patch at build time.
> >
> > What other schemes are being used out there?
>
> SuSE is doing the same, it looks like a kernel-2.6.19 as far as RPM is
> concerned.  But as this is in our "Kernel-of-the-day" section, it's not
> a big deal as long as the number keeps getting incremented properly for
> RPM to handle it.

Yeah, that's my thinking too.  But the reason I'm asking is
semi-related to a thread that came up on the fedora-devel list where
people whined about the RPM version being different than that of the
resulting kernel.  Also, the Fedora package munges SUBLEVEL and
EXTRAVERSION to match the RPM version.  Does SuSE also do this?

So I thought I would just see what the rest of the distros were doing.
Seems to be about a 50/50 mix so far.  Here's what I've found:

Gentoo: mm-sources-2.6.20_rc3-r1.ebuild
SuSE: <same naming scheme as Fedora>
Ubuntu: linux-source-2.6.20
Debian: dunno.  newest package I could find was 2.6.18

josh
-
To unsubscribe from this list: send the line "unsubscribe kernel-packagers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html