hyprwm/hyprland-plugins
1
0
Fork 0
mirror of https://github.com/hyprwm/hyprland-plugins.git synced 2024-11-22 02:35:57 +01:00
Code Issues Projects Releases Packages Wiki Activity
hyprland-plugins/flake.lock

212 lines
5 KiB
Text
Raw Permalink Normal View History

Nix: init
2023-04-27 00:58:01 +02:00
{
"nodes": {
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"hyprcursor": {
"inputs": {
"hyprlang": [
"hyprland",
"hyprlang"
],
"nixpkgs": [
"hyprland",
"nixpkgs"
],
"systems": [
"hyprland",
"systems"
]
},
"locked": {
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"lastModified": 1717181720,
"narHash": "sha256-yv+QZWsusu/NWjydkxixHC2g+tIJ9v+xkE2EiVpJj6g=",
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"owner": "hyprwm",
"repo": "hyprcursor",
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"rev": "9e27a2c2ceb1e0b85bd55b0afefad196056fe87c",
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"type": "github"
},
"original": {
"owner": "hyprwm",
"repo": "hyprcursor",
"type": "github"
}
},
Nix: init
2023-04-27 00:58:01 +02:00
"hyprland": {
"inputs": {
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"hyprcursor": "hyprcursor",
Nix: use mkHyprlandPlugin from nixpkgs
2024-03-07 10:29:46 +01:00
"hyprlang": "hyprlang",
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"hyprwayland-scanner": "hyprwayland-scanner",
Nix: init
2023-04-27 00:58:01 +02:00
"nixpkgs": "nixpkgs",
nix: use gcc13Stdenv for plugins
2023-10-04 11:08:57 +02:00
"systems": "systems",
Nix: init
2023-04-27 00:58:01 +02:00
"xdph": "xdph"
},
"locked": {
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"lastModified": 1717970802,
"narHash": "sha256-kFnaAmte/N1mrbHEQyrwDu9+laZzVAi4N2nQodCNfgg=",
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"ref": "refs/heads/main",
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"rev": "1423707dbefc0329e80895451903a77ab684f7ea",
"revCount": 4789,
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"submodules": true,
"type": "git",
"url": "https://github.com/hyprwm/Hyprland"
Nix: init
2023-04-27 00:58:01 +02:00
},
"original": {
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"submodules": true,
"type": "git",
"url": "https://github.com/hyprwm/Hyprland"
Nix: init
2023-04-27 00:58:01 +02:00
}
},
"hyprland-protocols": {
"inputs": {
"nixpkgs": [
"hyprland",
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"xdph",
Nix: init
2023-04-27 00:58:01 +02:00
"nixpkgs"
nix: use gcc13Stdenv for plugins
2023-10-04 11:08:57 +02:00
],
"systems": [
"hyprland",
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"xdph",
nix: use gcc13Stdenv for plugins
2023-10-04 11:08:57 +02:00
"systems"
Nix: init
2023-04-27 00:58:01 +02:00
]
},
"locked": {
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"lastModified": 1691753796,
"narHash": "sha256-zOEwiWoXk3j3+EoF3ySUJmberFewWlagvewDRuWYAso=",
Nix: init
2023-04-27 00:58:01 +02:00
"owner": "hyprwm",
"repo": "hyprland-protocols",
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"rev": "0c2ce70625cb30aef199cb388f99e19a61a6ce03",
Nix: init
2023-04-27 00:58:01 +02:00
"type": "github"
},
"original": {
"owner": "hyprwm",
"repo": "hyprland-protocols",
"type": "github"
}
},
[gha] Nix: update inputs
2023-12-29 01:25:01 +01:00
"hyprlang": {
"inputs": {
"nixpkgs": [
"hyprland",
"nixpkgs"
Nix: use mkHyprlandPlugin from nixpkgs
2024-03-07 10:29:46 +01:00
],
"systems": [
"hyprland",
"systems"
[gha] Nix: update inputs
2023-12-29 01:25:01 +01:00
]
},
"locked": {
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"lastModified": 1716473782,
"narHash": "sha256-+qLn4lsHU6iL3+HTo1gTQ1tWzet8K9h+IfVemzEQZj8=",
[gha] Nix: update inputs
2023-12-29 01:25:01 +01:00
"owner": "hyprwm",
"repo": "hyprlang",
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"rev": "87d5d984109c839482b88b4795db073eb9ed446f",
[gha] Nix: update inputs
2023-12-29 01:25:01 +01:00
"type": "github"
},
"original": {
"owner": "hyprwm",
"repo": "hyprlang",
"type": "github"
}
},
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"hyprwayland-scanner": {
"inputs": {
"nixpkgs": [
"hyprland",
"nixpkgs"
],
"systems": [
"hyprland",
"systems"
]
},
"locked": {
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"lastModified": 1717784906,
"narHash": "sha256-YxmfxHfWed1fosaa7fC1u7XoKp1anEZU+7Lh/ojRKoM=",
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"owner": "hyprwm",
"repo": "hyprwayland-scanner",
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"rev": "0f30f9eca6e404130988554accbb64d1c9ec877d",
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"type": "github"
},
"original": {
"owner": "hyprwm",
"repo": "hyprwayland-scanner",
"type": "github"
}
},
Nix: init
2023-04-27 00:58:01 +02:00
"nixpkgs": {
"locked": {
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"lastModified": 1717602782,
"narHash": "sha256-pL9jeus5QpX5R+9rsp3hhZ+uplVHscNJh8n8VpqscM0=",
Nix: init
2023-04-27 00:58:01 +02:00
"owner": "NixOS",
"repo": "nixpkgs",
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"rev": "e8057b67ebf307f01bdcc8fba94d94f75039d1f6",
Nix: init
2023-04-27 00:58:01 +02:00
"type": "github"
},
"original": {
"owner": "NixOS",
"ref": "nixos-unstable",
"repo": "nixpkgs",
"type": "github"
}
},
"root": {
"inputs": {
Nix: use mkHyprlandPlugin from nixpkgs
2024-03-07 10:29:46 +01:00
"hyprland": "hyprland",
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"nixpkgs": [
"hyprland",
"nixpkgs"
],
Nix: use mkHyprlandPlugin from nixpkgs
2024-03-07 10:29:46 +01:00
"systems": [
"hyprland",
"systems"
]
Nix: init
2023-04-27 00:58:01 +02:00
}
},
nix: use gcc13Stdenv for plugins
2023-10-04 11:08:57 +02:00
"systems": {
"locked": {
"lastModified": 1689347949,
"narHash": "sha256-12tWmuL2zgBgZkdoB6qXZsgJEH9LR3oUgpaQq2RbI80=",
"owner": "nix-systems",
"repo": "default-linux",
"rev": "31732fcf5e8fea42e59c2488ad31a0e651500f68",
"type": "github"
},
"original": {
"owner": "nix-systems",
"repo": "default-linux",
"type": "github"
}
},
Nix: init
2023-04-27 00:58:01 +02:00
"xdph": {
"inputs": {
treewide: add CMake files - Nix: switch everything to CMake - simplify overlay
2024-05-03 20:47:04 +02:00
"hyprland-protocols": "hyprland-protocols",
Nix: use mkHyprlandPlugin from nixpkgs
2024-03-07 10:29:46 +01:00
"hyprlang": [
"hyprland",
"hyprlang"
],
Nix: init
2023-04-27 00:58:01 +02:00
"nixpkgs": [
"hyprland",
"nixpkgs"
nix: use gcc13Stdenv for plugins
2023-10-04 11:08:57 +02:00
],
"systems": [
"hyprland",
"systems"
Nix: init
2023-04-27 00:58:01 +02:00
]
},
"locked": {
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"lastModified": 1716290197,
"narHash": "sha256-1u9Exrc7yx9qtES2brDh7/DDZ8w8ap1nboIOAtCgeuM=",
Nix: init
2023-04-27 00:58:01 +02:00
"owner": "hyprwm",
"repo": "xdg-desktop-portal-hyprland",
flake: overlay: move packages to `hyprlandPlugins` namespace (#180) * flake: inputs: follow hyprland/nixpkgs The reason to do this instead of `inputs.hyprland.nixpkgs` or inheriting that attribute is for the semantic meaning of having it in the `flake.lock`. This makes it obvious that it can be overridden. * flake: overlay: adopt nixpkgs hyprlandPlugins I have introduced the `hyprlandPlugins` namespace to this flake's default overlay. Derivations are moved there, in-line with Nixpkgs. I recommend that other Hyprland plugin flake authors use the same pattern: ```nix overlays = { default = self.overlays.your-plugin-name; your-plugin-name = final: prev: { hyprlandPlugins = prev.hyprland-plugins or {} // { your-plugin-name = final.callPackage ./nix/default.nix {}; }; }; }; ``` Your flake's packages output should also make use of this overlay via a manual `nixpkgs` import, and inherit the outputs from `pkgs.hyprlandPlugins`. This will ensure that the flake's dependency graph is properly reflected in the derivation outputs. * gitignore: add nix build results * flake: inputs: update all
2024-06-11 15:05:05 +02:00
"rev": "91e48d6acd8a5a611d26f925e51559ab743bc438",
Nix: init
2023-04-27 00:58:01 +02:00
"type": "github"
},
"original": {
"owner": "hyprwm",
"repo": "xdg-desktop-portal-hyprland",
"type": "github"
}
}
},
"root": "root",
"version": 7
}
Reference in a new issue Copy permalink