reopen 402141 thanks > This is by design.
I think this design is flawed, and the very purpose of this bug report is to discuss this, not to be told that it is like it is. > The files are available in the common case > of the user compiling and installing the images on the same machine; > and then building third party modules. In the case the image is > installed on another machine, the symlink is removed on installation, > so no harm done. Okay, so at least that logic is fine. However, I still think that this symlink is problematic. It is highly likely that the files at /home/frank/src/linux/ are not the source of the kernel package that installed a symlink into /lib/modules/<version>/source. I think this is particularly true for users who actually use kernel-package to manage their home-built kernels: They'll probably have multiple kernel packages with different version installed, and what's currently unpacked in their usual source dir is a matter of chance. Moreover, I'm surprised that this is supposed to be related to compiling third-party tools. README.modules doesn't say anything about having this symlink AFAICT, it doesn't mention that it makes a difference whether the kernel image package is already installed when building third-party modules, or not. What's the function of that link? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
