On Wed, 2004-11-17 at 12:13 -0500, Dave Jones wrote: > > > I could do something really ugly, and just bump the > > > devel kernels up past the last released FC3 kernel > > > each time I do an update, but that is a little sick. > > > > Well, here's a suggestion that you might want to shoot down as stupid > > and uninformed: How about using the first digit of the release tag? What > > does it actually mean for the kernel - for other packages it's certainly > > just a serial number... Why not bump it to "4" right away, and then let > > that digit spill over to the stable FC4 kernels when Rawhide takes off > > on the "5" path. Alternatively, of course, there's some deep meaning to > > the number "1" which prevents this from being sane at all. > > You mean use 2.6.9-4.650 ? Yes, that was my thought. > unfortunatly the '1.650' is the CVS tag. > without some creative forking, its not going to work. OK, so the "1" is actually relevant then. So how about just sticking the the distribution version before the current release tag? That would make your next hypothetical -1.650 be tagged -4.1.650; you can still keep the full CVS tag in there. I guess this is similar in some sense to what Satish suggested further along in the thread, but not as lengthy. And definitely not as ugly as keeping the distro name in the package name, which seems like a horrible upgrade mess if nothing else... I'm probably still missing something? /Per -- Per Bjornsson <perbj@xxxxxxxxxxxx> Ph.D. Candidate, Department of Applied Physics, Stanford University