Hi Josselin: As I understand, the dpkg maintainer (Michael Vogt) is implementing the idea of package groups that have sticky dependencies. This should mean that when a package gets installed, it will need to register with the package group. When a kernel with a new ABI is available, it won't be offered as an upgrade until all of the items in the package group are available for the upgrade. I've added him on to try to comment on this some more. Josselin Mouette wrote: > Le jeudi 11 septembre 2008 à 17:29 +0200, David Paleino a écrit : > > > This is definitely the correct way to build extra modules. This could > mean: > * The end of the nightmare for users who need to rebuild their > modules by hand every time the kernel ABI changes. > * More smoothness for testing migration of non-free modules, which > could simply be shipped as source. > > Please go ahead in this direction. > > One of the issues I’m wondering about is: how do you ensure you always > have the kernel headers for the installed kernels? > > Cheers, > -- Mario Limonciello *Dell | Linux Engineering* mario_limonciello@dell.com
Attachment:
signature.asc
Description: OpenPGP digital signature