diff options
| author | Maximilian Bosch <maximilian@mbosch.me> | 2022-12-06 13:47:40 +0100 |
|---|---|---|
| committer | Maximilian Bosch <maximilian@mbosch.me> | 2022-12-06 14:04:13 +0100 |
| commit | fcf0e540b16eb487e7bf131e52d8002e643aeb5e (patch) | |
| tree | e85566d1fe7d3dc048461db7c99d15495660a21c /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 387779ef691b7f18e4d22f36411fa9af9c459cbc (diff) | |
nixos/manual: document kernel backporting policy and implications of it
I'm well aware that this issue is currently under discussion[1] and that
these things may change. Also, please don't misinterpret this as an
attempt to end the discussion.
This topic made it obvious that people are surprised by the way this
issue is handled and only finding out about this unwritten rule because
of asking is not a good state IMHO, so I decided to document the
following things:
* Right now we drop kernels as soon as they get out of maintenance (LTS
kernels even before the next stable NixOS that will exceed their
lifespan).
* The `latestCompatibleLinuxPackages` attribute from ZFS isn't
monotonic since latest only refers to the latest supported kernel.
* In fact `latestCompatibleLinuxPackages` doesn't seem to be documented
at all in the manual, so I also did that.
[1] https://discourse.nixos.org/t/aggressive-kernel-removal-on-eol-in-nixos/23097
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions