| 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.
|
|
|
This is a simple script, there's no benefit in having this in go. Having
it Python makes it easier to extend with panda or other libraries in the
future if I need more statistics too.
|