diff options
| author | Joachim Fasting <joachifm@fastmail.fm> | 2016-04-18 23:09:21 +0200 |
|---|---|---|
| committer | Joachim Fasting <joachifm@fastmail.fm> | 2016-04-19 14:45:40 +0200 |
| commit | 1414f902708ecd979f2cf7f6fe46c3f4b650b594 (patch) | |
| tree | c49bd42003fbb8526a2643e7b1ed31a5acbda0fa /pkgs/development/python-modules/GitPython/hardcode-git-path.patch | |
| parent | faf63d15249f7eaed676a8fa097c3e734e61249d (diff) | |
linuxPackages: remove kernelHeaders
User-space programs should not be using headers extracted from random
kernels, but should in fact use the headers that were used to build
libc; see e.g., this LKML posting by Linus Torvalds on the subject of
Linux API headers at [1].
What is more, the Linux API headers are supposed to be backwards
compatible[2], so there's really no good reason to have more than one
such package, namely the latest one required by a package in our tree.
That is, `kernelHeaders` is not only incorrect but serves no real
purpose: out-of-tree modules use the sources provided by `kernel.dev`;
user space should use `stdenv.cc.libc.linuxHeaders` or the top-level
`linuxHeaders` attribute.
Apart from klibc, nothing in nixpkgs used `linuxPackages.kernelHeaders`,
so the impact of this change is minimal.
[1]: http://lkml.iu.edu/hypermail/linux/kernel/0007.3/0587.html
[2]: https://www.kernel.org/doc/Documentation/kbuild/headers_install.txt
Diffstat (limited to 'pkgs/development/python-modules/GitPython/hardcode-git-path.patch')
0 files changed, 0 insertions, 0 deletions
