Redundant nixpkgs instances

[musjj]

This flake instantiates redundant nixpkgs instances, even with follows:

• Added input 'neovim-nightly/hercules-ci-effects/flake-parts/nixpkgs-lib':
    'github:NixOS/nixpkgs/4bc72cae107788bf3f24f30db2e2f685c9298dc9?dir=lib' (2023-06-29)
• Added input 'neovim-nightly/hercules-ci-effects/hercules-ci-agent/nixpkgs':
    'github:NixOS/nixpkgs/0fbe93c5a7cac99f90b60bdf5f149383daaa615f' (2023-07-02)

Can we add follows to this flake to prevent this? I tried looking over the flake.nix, but I'm not sure where the flake-parts input is coming from.

[musjj]

This seems to work for me:

diff --git a/flake.nix b/flake.nix
index 40073a1..356a50d 100644
--- a/flake.nix
+++ b/flake.nix
@@ -1,8 +1,12 @@
 {
   description = "Hercules CI Effects";
 
-  inputs.nixpkgs.url = "github:NixOS/nixpkgs";
-  inputs.hercules-ci-agent.url = "hercules-ci-agent";
+  inputs = {
+    nixpkgs.url = "github:NixOS/nixpkgs";
+    hercules-ci-agent.url = "hercules-ci-agent";
+    hercules-ci-agent.inputs.nixpkgs.follows = "nixpkgs";
+    flake-parts.inputs.nixpkgs-lib.follows = "nixpkgs";
+  };
 
   outputs = inputs@{ self, nixpkgs, hercules-ci-agent, flake-parts, ... }:
     flake-parts.lib.mkFlake { inherit inputs; }

I haven't tested anything beyond nix flake lock though. Any thoughts?

[roberth]

This will be a non-issue after

• Reuse input lock files NixOS/nix#7730

[roberth]

Have followed about as much as possible. You could add a follows for the remaining nixpkgs input, although that's not quite as robust as not doing it. Should be fine most of the time.