python3Packages.lttng: init at 2.13.11#285390
Conversation
bjornfor
left a comment
There was a problem hiding this comment.
LGTM.
The two commits can be squashed.
|
Maybe you can amend the commit and say in the commit body why this is a separate attribute which rebuilds lttng-tools, instead of adding python support directly to lttng-tools? (I'm guessing it's about closure size?) |
0e156ba to
93a6158
Compare
Done and done. |
93a6158 to
33972b4
Compare
|
I have switched to using the |
Thanks.
Why is putting a build input in nativeBuildInputs "polluting" it? Using those variables seem more complicated to me. Or am I missing something? Nit: Commit messages should be wrapped at 72 chars to avoid overlong lines. |
Nix treats |
Put that in a code comment maybe? |
A new attribute overriding lttng-tools is created, rather than enabling Python support in lttng-tools itself, in order to reduce the closure size and leave lttng-tools Python-version-agnostic.
33972b4 to
d38fa22
Compare
|
I have added the comment and wrapped commit messages to 72 lines. |
Description of changes
This package contains Python bindings to
liblttng-ctlfrom LTTng‑tools.Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.
@bjornfor