On 08.04.2009 20:33, Nicolas Chauvet wrote:
2009/4/8 Richard Shaw <[email protected]>:
>
Presumably if there was no need then the package would not exist,
akmod is made when you build your own kernel or when you want a
special version of a kmod and prevent it from beeing updated.
People are free to use akmods in the way they want.
Further: The use case "normally let kmod-foo tracks in kmod-foo-$(uname
-r) for the latest kernels and have the akmods-foo package installed to
jump in when needed IMHO is perfectly valid.
IOW: I don't agree to that statement quoted above.
right? I use it because the kmod packages are not always available
wrong - it is usually available "before" the kernel hit the stable
repository (which lead to other kind or interaction problem, but could
be workarounded by a plugin).
Usually yes, but not always :-/ And the infrastructure problem your
point at here works in both ways. So from the users point of view it
sometimes might look like we haven't released kmods for a new kernel
when in fact we have.
CU
knurd
