| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The convention is to use `pkgs` or `packages` for overlays and
definition of custom packages. Since I'm already using `pkg` for go,
I prefer to use `packages` for my scripts.
|
| |
|
| |
|
|
|
|
|
|
|
| |
For the python tools, we need the python runtime to be available. For
this we need to specify the dependencies in `propagatedBuildInputs`.
The same is true for flamegraph and perf.
|
|
I don't want to inline shell scripts inside nix configuration, as it
prevents me to use `shellcheck` to validate them for example.
The script is now moved into the tool directory, and is a tiny bit more
flexible, so that I can run it as my own user.
|