spec hacks for vanilla and git-based kernel rpm builds

[Thorsten Leemhuis]

On 02.07.2007 18:27, Dave Jones wrote:
> On Mon, Jul 02, 2007 at 11:00:59AM -0500, Josh Boyer wrote:
>  > On Mon, 2007-07-02 at 11:57 -0400, Dave Jones wrote:
>  > > On Mon, Jul 02, 2007 at 11:51:02AM -0400, Jarod Wilson wrote:
>  > > 
>  > >  > Also, anyone have thoughts on re-versioning, at least in the vanilla
>  > >  > case, so as to more accurately describe what's being built? For example,
>  > >  > the above is 2.6.22-rc4-git6, so I'm a fan of the package that gets
>  > >  > churned out being kernel-vanilla-2.6.22-0.1.rc4.git6.fc8 or some such
>  > >  > thing, instead of kernel-vanilla-2.6.21-1.3243.fc8.
>  > > 
>  > > I'd like to give this a shot for f8.  Doing it for the -vanilla packages
>  > > is a 'must-have', and if it works out there, there's no reason not
>  > > to do it in all the packages.
> There's another reason I'd like to get this done for F8.
> I'd still really like us to ship 2.6.23 for f8, but with the shorter
> devel schedule, it's unclear if it's going to land upstream in time.
> We've shipped -rc's as GA kernels before, but I always felt 'dirty' for
> doing this (especially when we name them incorrectly).

I'd say it's unlikely that 2.6.23 is not ready in time for F8. Some
statistics that lead to my opinion:

2.6.18 took 94 days to develop
2.6.19 took 71 days
2.6.20 took 66 days
2.6.21 took 80 days

2.6.22 is about 5-7 days away afaics; so it will have had around 73 days
to get finished.

Final devel freeze for F8 currently is 24 October 2007 -- that's 114
days away from now; minus those ~6 days until 2.6.22; that leaves around
108 days for 2.6.23 to mature in time for the F8 freeze. I'd say that
should work out when I look at the numbers from recent kernels found above.

> Shipping it with 'rc3' or whatever in the title seems a little more
> honest at least about what we're shipping, and at the same time,
> it prevents bad reviewers from writing "Fedora still ships with a 2.6.22
> kernel".

A proper kernel naming would help there as well (e.g. name the kernels
just as upstream -- e.g. 2.6.23-rc[1-7]{,.git[0-9]*). ;-) Yeah, this old
topic again that never got solved.

CU
thl