There are only four items in the linuxPackages
attribute set, although there are more than two dozen different variations of this attribute set.
For a darwinPackages
attribute set I think these items are obvious candidates:
nixpkgs.osxfuse
nixpkgs.macvim
nixpkgs.darwin.trash
nixpkgs.wxmac
nixpkgs.pinentry_mac
I’m a little hesitant about the last one because there are several pinentry implementations, so it might seem inconsistent to move one of them to a different attribute set, but on the other hand, it is a macOS application (.app
) that can only be installed on macOS.
Less sure about this stuff, although it does list darwin as platform requirement:
nixpkgs.gtk-mac-bundler
nixpkgs.gtk-mac-integration
nixpkgs.gtk-mac-integration-gtk2
nixpkgs.qt5.qtmacextras
nixpkgs.qt512.qtmacextras
nixpkgs.qt59.qtmacextras
And then there is this, but it seems auto-generated, is already in its own attribute set, and I think it exists only for nix-shell
:
nixpkgs.rubyPackages_2_4.osx_keychain
nixpkgs.rubyPackages_2_5.osx_keychain
nixpkgs.rubyPackages_2_6.osx_keychain
Should we prepare a PR for putting the first five packages into its own attribute set?
I do think it would be nice to query mac-specific packages, hence why I would suggest doing this instead of moving trash
to the root attribute set.
Doing a search for mac stuff is difficult because things can be named osx, mac, darwin, or neither.
As for name, perhaps macPackages
would be better than darwinPackages
? After all, macvim
, pinentry_mac
, and wxmac
require the window manager.