summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
diff options
context:
space:
mode:
authorMaximilian Bosch <maximilian@mbosch.me>2025-09-29 12:13:05 +0200
committerMaximilian Bosch <maximilian@mbosch.me>2025-10-24 18:06:29 +0200
commit1965f3c77d37f0f03b77ebb9095a9222646baeb5 (patch)
tree2d88acb6c75e5322ec6f2ea7cd21137dde593293 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
parent845e340ed98ef6d8a5c5d7069663f2cd034e508a (diff)
linux: manual-config.nix -> build.nix
Since I started touching this subsystem, I found the name confusing since this is the part where we actually compile the kernel and we have a ready-to-use configuration. The stated goal of the commit introducing it[1] is to provide a function to > make it possible to build a kernel with a user provided .config. Considering that this is supposed to be a differentiation from other build mechanisms and nowadays this is the only way to build kernels in nixpkgs, I figured that `build.nix` is a better name. `pkgs.linuxManualConfig` isn't renamed on purpose: Kloenk and I are planning to do more involved work and it may become necessary to change parts of the API. So asking users to do a migration now just to add another one soon isn't worth it. [1] bf7467cbb1f08470854db73ee2c07d9f896aefc8
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions