G'day, I was working on a treewide PR to move packages to by-name & format via nixfmt-rfc-style until I was informed that such PRs are actually discouraged in favor of https://github.com/NixOS/nixpkgs/pull/211832.

Are there any other ongoing processes that I can lend a hand with? Or things I can help speed up by making a series of PRs? Otherwise I plan to go forward with adding licenses to most of the packages listed here but I'd be happy to help with higher-priority issues if there are any.

emily@yuyuko ~/D/nixpkgs ((8e484a4c))> ls pkgs/*/*/default.nix | wc -l
     965
emily@yuyuko ~/D/nixpkgs ((8e484a4c))> for file in pkgs/*/*/default.nix; test (count (dirname $file)/*) = 1 && echo x; end | wc -l
     660

In reply to @philiptaron:matrix.org

When I run maintainers/scripts/check-by-name.sh master locally in my nixpkgs repository, without any changes, I get this error:

I/O error:  Failed to get the definition info for attribute acl: In /tmp/tmp.bQmCobXFGj/merged/pkgs/stdenv/linux/default.nix, attribute parent node is not an attribute path node: NODE_INHERIT@28432..28603

Does anyone else reproduce this? It appears to be about this line in pkgs/stdenv/linux/default.nix:

inherit (prevStage)
          gzip bzip2 xz bash coreutils diffutils findutils gawk
          gnused gnutar gnugrep gnupatch patchelf
          attr acl zlib libunistring;

In reply to@emilazy:matrix.org
(I would certainly be happy to see those go, as they obviously don't compose)

In reply to @emilazy:matrix.org
I sort of imagine we want a world where it looks like stdenv.mkDerivation { mixins = [ qtMixin pythonMixin ]; … } or something

both buildRustPackage and buildPythonPackage can be replaced with stdenv.mkDerivation and adding the appropriate setup hooks to nativeBuildInputs (e.g. cargoSetupHook or pypaSetupHook). i think the qt5.callPackage stuff is in a similar state.

the Python folk seem very against the idea of replacing buildPythonPackage with mkDerivation. i think there's more appetite for that on the Rust front.

In reply to @emilazy:matrix.org
I sort of imagine we want a world where it looks like stdenv.mkDerivation { mixins = [ qtMixin pythonMixin ]; … } or something

both buildRustPackage and buildPythonPackage can be replaced with stdenv.mkDerivation and adding the appropriate setup hooks to nativeBuildInputs (e.g. cargoSetupHook or pypaBuildHook). i think the qt5.callPackage stuff is in a similar state.

the Python folk seem very against the idea of replacing buildPythonPackage with mkDerivation. i think there's more appetite for that on the Rust front.