On Thu, Mar 24, 2011 at 11:24 PM, Florian Pritz <[email protected]> wrote: > On 24.03.2011 08:50, Jason Melton wrote: >> 2011/3/24 Ng Oon-Ee <[email protected]>: >>> On Thu, 2011-03-24 at 12:16 +0900, Jason Melton wrote: >>>> Hello, >>>> >>>> Over on the rtl8192se package[1], we have been discussing how to best >>>> support DKMS in packaging (at the AUR level), and I would like to ask >>>> for wider and more experienced comments. I have put my thoughts here >>>> and in more detail on my personal Arch wiki page[2]. >>> >>> Quick problem, what happens when the kernel version updates? For example >>> modules are currently in /lib/modules/2.6.38-Arch/kernel/* (from >>> [testing]) but when 2.6.39 comes out the location changes, and the >>> package needs to be reinstalled in any case. >>> >> A drawback is that, in this case DKMS will create a file that is no >> longer tracked by pacman. But, since an updated package must be >> released soon anyway for the non-DKMS users, this situation will not >> last long. An alternative would be updating the information in the >> pacman db, but that's really pushing things I think. > > Packages that contain kernel modules should contain something like > depends=(kernel26>=2.6.37 kernel26<2.6.38) so unless you use -d or there > is an updated version of the package you shouldn't be able to update the > kernel.
True, but this doesn't take away any of the benefits of DKMS support.
