Bug#521515: linux-headers-2.6.29-1-amd64: please restore symlinks into -common

[lsorense@csclub.uwaterloo.ca (Lennart Sorensen)]

On Sat, Mar 28, 2009 at 11:28:07PM +0100, Bastian Blank wrote:
> severity 521515 wishlist
> tags 521515 wontfix
> thanks
> 
> On Fri, Mar 27, 2009 at 09:02:04PM -0400, Aaron M. Ucko wrote:
> >                                     As of 2.6.29-1, that no longer
> > holds, causing trouble for packages such as openafs-modules-source that
> > don't entirely defer to the kbuild framework.
> 
> There is no reliable way to detect the include paths of the kernel
> without using kbuild.
> 
> >                  but would appreciate it if you could please reinstate
> > the symlinks in the flavor-specific linux-headers packages.
> 
> Nope. At least not until you show that it breaks the _documented_ usage.

Out of couriosity (and to try and fix the nvidia driver build system)...
Documented by who?  Debian or the linux kernel?

It seems openafs, vmware, nvidia, and probably many others,
rely on the idea that there is a single directory with all the
kernel headers as configured for the current running kernel in
/lib/modules/<version>/build/, which was true up until the debian 2.6.29
linux-headers got released.

So did this change improve anything?  It certainly has made a lot of
work for a lot of people for what appears to have no benefit so far.

So where is the correct way to use kernel headers documented?

-- 
Len Sorensen