[elrepo-devel] Two things about kversion

[Farkas Levente]

On 04/20/2010 03:29 AM, Akemi Yagi wrote:
> Hi all,
>
> 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.

i vote for the oldest possible version which is good enough to build it 
and hardcode it into the spec file. otherwise it very difficult to build 
in mock since in mock uname -r is NOT the chrooted env's kernel but the 
host machine's release and it cause eg. for me a lots of headache 
(building fedora kmod on a centos build farm is rather tricky thing).

-- 
   Levente                               "Si vis pacem para bellum!"