[repo-coord] kernel module versioning (was: Blackmailing ...)

[Fernando Pablo Lopez-Lezcano]

> > > To clueless me it doesn't sound terribly broken....
> > 
> > It isn't. You are confused, because both start with "kernel-module-",
> > but the one Dag promotes has the kernel data in rpm's release tag, not
> > the name tag. This severely breaks any upgrade paths as discussed in
> > these old threads above.
> 
> It doesn't break the upgrade path, and you seem to like 'overstating' 
> things by using wordings like 'breaking severly' etc...

Most probably there is some difference as to what "upgrade path"
actually means, the following example highlights one instance of
breakage (this is not the whole story, of course, just one example):

  apt-get install kernel#x.x.x-1
does the equivalent of a rpm -ivh
  apt-get install kernel-module-alsa#1.0.4-1_x.x.x
also does the equivalent of a rpm -ivh because you have to be able to
install multiple instances of kernel-module-alsa for different kernels

Now a new version of alsa for kernel x.x.x is released. An upgrade will
fail because kernel-module-1.0.5-1_x.x.x will have conflicting files
with the already installed kernel-module-alsa-1.0.4-1_x.x.x. That is,
apt-get install kernel-module-alsa#1.0.5-1_x.x.x will fail. 

So, from my point of view, the upgrade path is broken (with the existing
user tools). 

-- Fernando