summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/GitPython/hardcode-git-path.patch
diff options
context:
space:
mode:
authorJoachim Fasting <joachifm@fastmail.fm>2016-05-03 19:24:40 +0200
committerJoachim Fasting <joachifm@fastmail.fm>2016-05-04 01:07:53 +0200
commit0bd31bce10dbcfa90a5e82f4f6c1bdc1252d02ae (patch)
treee536611aab4d2481041c4d5896ca830a923b5cd8 /pkgs/development/python-modules/GitPython/hardcode-git-path.patch
parentd6e4c1b750be049227870bc635d28acc46033d0e (diff)
grsecurity: drop support for 4.4 kernels
From now on, only the testing branch of grsecurity will be supported. Additionally, use only patches from upstream. It's impossible to provide meaningful support for grsecurity stable. First, because building and testing \(m \times n \times z) [1], packages is infeasible. Second, because stable patches are only available from upstream for-pay, making us reliant on third-parties for patches. In addition to creating yet more work for the maintainers, using stable patches provided by a third-party goes against the wishes of upstream. nixpkgs provides the tools necessary to build grsecurity kernels for any version the user chooses, however, provided they pay for, or otherwise acquire, the patch themselves. Eventually, we'll want to remove the now obsolete top-level attributes, but leave them in for now to smoothe migration (they have been removed from top-level/release.nix, though, because it makes no sense to have them there). [1]: where \(m\) is the number of grsecurity flavors, \(n\) is the number of kernel versions, and z is the size of the `linuxPackages` set
Diffstat (limited to 'pkgs/development/python-modules/GitPython/hardcode-git-path.patch')
0 files changed, 0 insertions, 0 deletions