[elrepo-devel] Two things about kversion

[Alan Bartlett]

On 20 April 2010 02:29, Akemi Yagi <toracat at elrepo.org> wrote:

> I would like to start a discussion about a couple of things regarding
> "kversion".
>
> (1) Which version of kernel should a kmod package be built against?
>
> Many kmod packages provided by ELRepo are compatible through all
> versions of kernel within CentOS 5.x thanks to the kABI. However,
> there are those that are valid only with certain version and up.  So,
> the question arises: should we always build a kmod package against the
> oldest possible kernel -- or the newest possible --or -- ?
>
> (2) Is it a good idea to hardcode the kversion in the spec file?
>
> This question is related to the first one. It is not instantly obvious
> which kernel was used as a base for a given kmod.  Hardoding the
> kversion in the spec file would make it easy to identify it.  Another
> reason (and this may be more important) is that mock can be used for
> building if kversion is defined in the spec.
>
> Please let me know your thoughts.

My initial thought is "What a coincidence!" -- as I have just started
a policy of noting, at the head of the .spec file, which "build-base"
kernel has been used for the package's build. Please see the
dahdi-kmod-2.3.0-1.*.src.rpm file, currently in elrepo-testing, as an
example.

Alan.