bug: Shouldn't programs.swaylock.package allow null?

[s0racat]

Are you following the right branch?

• [X] My Nixpkgs and Home Manager versions are in sync

Is there an existing issue for this?

• [x] I have searched the existing issues

Issue description

swaylock requires additional configuration for non NixOS and non-sway environments. Shouldn't such things be left to NixOS and the system?

Maintainer CC

@rcerc

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.6.60, NixOS, 24.11 (Vicuna), 24.11.20241113.24f0d4a`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.24.10`
 - nixpkgs: `/nix/store/c05d1sqfhkl93p3j5ykic68mgg1gsrvb-source`

[rcerc]

Thanks for reporting! I have filed #6095 to change this. In the meantime, you could set

package = pkgs.runCommandLocal "dummy" { } "mkdir $out";

Edit: Better alternative suggested below: pkgs.emptyDirectory.

[s0racat]

Thank you!

[rycee]

Instead of the pkgs.runCommandLocal … alternative above you can simply use pkgs.emptyDirectory. I think this is preferred in general over using a null.

[rcerc]

@rycee, I did not know about that! #6095 should be closed then?

[s0racat]

I understood. I will close this issue.