* 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
