[Pkg-virtualbox-devel] Bug#475542: Bug#475542: Bug#475542: virtualbox-ose-source should not depend on prebuild kernel packages

[arne anka]

> As far as I've understand that:
>  - Arne has a home-build kernel (not with make-kpkg but with make && make
> install
>  - Arne want's to build a kernel module with m-a
>
> Arne, please correct me if I'm wrong.

this is correct.

> A mixture between dpkg build kernel /modules and home build kernel /
> modules is in my eyes not supported. (and can't be supported).

and that's the point i do not understand.
i did and do it with several source-packages for years on end without ever  
having a problem.
the only thing i need to do, was removing the dependency lines.
thus i have everything under control - the kernel lives at its own space  
and is easily replaced and all additional modules build from the souces  
are managed by dpkg.
it is a perfect solution (in theory) because the sources of those modules  
are updated by apt and the packages are created and installed by m-a and  
thus managed by apt/dpkg, too.
there are no files lounging around not belonging to either the kernel  
itself or a trackable debian package.

the only point i see, where something could be wrong would be if the  
kernel&modules was installed at some non-standard place instead of /boot  
and /lib/modules/KVERS/ -- but who would do such a thing?

i see your point in ensuring smooth upgrades but i still think there must  
be a way to reconcile both -- maybe m-a should do some checks and/or ask  
the user wether those dependencies are to include or not or something like  
that ...