[ATrpms-devel] kmdl naming scheme (was: nvidia on smp kernels)

[Axel Thimm]

On Sat, Dec 18, 2004 at 03:26:08PM -0800, Keith Irwin wrote:
> On Sat, 2004-12-18 at 15:02 -0800, Jarod Wilson wrote:
> > On Saturday 18 December 2004 14:35, Keith Irwin wrote:
> > > Is there something I can do to get this working for SMP with the current
> > > yummable infrastructure?
> 
> > I'm not a regular yum user, but this apt line would work, assuming you're 
> > using the latest FC3 errata smp kernel:
> 
> > # apt-get install kernel-module-nvidia-graphics6629-2.6.9-1.681_FC3smp
> 
> Well there you go. I was looking and nvidia*. ;)

Which has happened quite a lot of time since ATrpms switched from

foo-kmdl-<kernelversionrelease>-<fooversion>-<foorelease>

to

kernel-module-foo-<kernelversionrelease>-<fooversion>-<foorelease>

The idea was that changing to the latter "standard" would ease
inter-repo communication on kernel module packaging.

This was more than half a year ago, there was no further convergence,
and even worse most repos stopped building kernel module rpms at all
(the rather peculiar decisions the kernel rpm maintainer made about
the kernel-source rpm were one of the reasons).

So I'm thinking on whether this "standard" was wise to follow and
whether we should revise it now. The advantages of the kmdl naming is that

o foo kernel modules are lexically grouped with the foo userland rpms,
o the kernel version/release is attached to the kernel module string,
  not foo (there were reports on "foo is at version 2.6.9?")
o shorter is better

The disadvantages are that it leaves the "standard" which currently it
was rather the sole implementation of ...

Thoughts?
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20041219/d0efd292/attachment.bin