On Mon, 17 Nov 2008 19:21:00 +0100
Thomas Bächler
Mads Michelsen schrieb:
So I guess my questions are: 1) Is there some way around the module becoming outdated with each and every kernel update? and if not
You only have to rebuild with major updates (which happen every 3 months).
2) For myself, I can just keep the source code on my drive and rebuild it whenever this happens - but is there some way of altering the PKGBUILD to do the same? 3) Any other way around the issue apart from quickly updating the package whenever there's a kernel upgrade?
All you can do is prevent anyone from accidently updating:
depends=('kernel26>=2.6.27' 'kernel26<2.6.28')
Once a major update occurs, pacman will refuse to update the kernel26 package unless you -Ud a newer one (with correct depends) first.
Thanks for the replies. I just had the opportunity to test it with 2.6.27.6-1 and the old module still works, like Aaron said - where I thought I'd noticed previous minor upgrades reject it (strange...) - so that's some comfort. I'll use Thomas' suggestions of depends=('kernel26>=2.6.27' 'kernel26<2.6.28') - I think I preivously tried kernel26=2.6.27 but I believe that was interpreted very literally.