nix-community/nixos-generators
1
1
Fork 0
mirror of https://github.com/nix-community/nixos-generators.git synced 2024-11-29 15:04:11 +03:00
Code Issues Packages Projects Releases Wiki Activity
5320ff5dcf
nixos-generators/flake.lock

44 lines
1.0 KiB
Plaintext
Raw Normal View History

Create flake.nix
2020-10-23 17:48:17 +03:00
{
"nodes": {
For module-only consumers, avoid depending on nixpkgs This seems odd, but it works since input dependencies are lazily fetched that means a downstream repo, that only consumes the modules output (like for example `divnix/digga`), does never fetch nor instantiate nixpkgs proper (which would be costly). This enables `divnix/digga` to continue to _not_ depend on `nixpkgs` for operation. (it still depends on `nixpkgs` as a strict development dependency, but beacause of the black magic which I describe above, no end user will ever fetch it's depenency on `nixpkgs`. So, here, we want to implement a similar trick to avoid acquireing deps where they should net be acquired.
2021-06-17 02:00:15 +03:00
"nixlib": {
"locked": {
Bump cachix/install-nix-action from 14 to 15 Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 14 to 15. - [Release notes](https://github.com/cachix/install-nix-action/releases) - [Commits](https://github.com/cachix/install-nix-action/compare/v14...v15) --- updated-dependencies: - dependency-name: cachix/install-nix-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-15 16:02:51 +03:00
"lastModified": 1636849918,
"narHash": "sha256-nzUK6dPcTmNVrgTAC1EOybSMsrcx+QrVPyqRdyKLkjA=",
flake.lock: Update (#109) Flake input changes: * Updated 'nixlib': 'github:divnix/nixpkgs.lib/95c4b09c919abfbadc24386008541db16ba712d8' -> 'github:nix-community/nixpkgs.lib/7b4dc08734c5c4703b22b9c780417042e1c8f020'
2021-06-29 16:35:46 +03:00
"owner": "nix-community",
For module-only consumers, avoid depending on nixpkgs This seems odd, but it works since input dependencies are lazily fetched that means a downstream repo, that only consumes the modules output (like for example `divnix/digga`), does never fetch nor instantiate nixpkgs proper (which would be costly). This enables `divnix/digga` to continue to _not_ depend on `nixpkgs` for operation. (it still depends on `nixpkgs` as a strict development dependency, but beacause of the black magic which I describe above, no end user will ever fetch it's depenency on `nixpkgs`. So, here, we want to implement a similar trick to avoid acquireing deps where they should net be acquired.
2021-06-17 02:00:15 +03:00
"repo": "nixpkgs.lib",
Bump cachix/install-nix-action from 14 to 15 Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 14 to 15. - [Release notes](https://github.com/cachix/install-nix-action/releases) - [Commits](https://github.com/cachix/install-nix-action/compare/v14...v15) --- updated-dependencies: - dependency-name: cachix/install-nix-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-15 16:02:51 +03:00
"rev": "28a5b0557f14124608db68d3ee1f77e9329e9dd5",
For module-only consumers, avoid depending on nixpkgs This seems odd, but it works since input dependencies are lazily fetched that means a downstream repo, that only consumes the modules output (like for example `divnix/digga`), does never fetch nor instantiate nixpkgs proper (which would be costly). This enables `divnix/digga` to continue to _not_ depend on `nixpkgs` for operation. (it still depends on `nixpkgs` as a strict development dependency, but beacause of the black magic which I describe above, no end user will ever fetch it's depenency on `nixpkgs`. So, here, we want to implement a similar trick to avoid acquireing deps where they should net be acquired.
2021-06-17 02:00:15 +03:00
"type": "github"
},
"original": {
flake.lock: Update (#109) Flake input changes: * Updated 'nixlib': 'github:divnix/nixpkgs.lib/95c4b09c919abfbadc24386008541db16ba712d8' -> 'github:nix-community/nixpkgs.lib/7b4dc08734c5c4703b22b9c780417042e1c8f020'
2021-06-29 16:35:46 +03:00
"owner": "nix-community",
For module-only consumers, avoid depending on nixpkgs This seems odd, but it works since input dependencies are lazily fetched that means a downstream repo, that only consumes the modules output (like for example `divnix/digga`), does never fetch nor instantiate nixpkgs proper (which would be costly). This enables `divnix/digga` to continue to _not_ depend on `nixpkgs` for operation. (it still depends on `nixpkgs` as a strict development dependency, but beacause of the black magic which I describe above, no end user will ever fetch it's depenency on `nixpkgs`. So, here, we want to implement a similar trick to avoid acquireing deps where they should net be acquired.
2021-06-17 02:00:15 +03:00
"repo": "nixpkgs.lib",
"type": "github"
}
},
Create flake.nix
2020-10-23 17:48:17 +03:00
"nixpkgs": {
"locked": {
Bump cachix/install-nix-action from 14 to 15 Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 14 to 15. - [Release notes](https://github.com/cachix/install-nix-action/releases) - [Commits](https://github.com/cachix/install-nix-action/compare/v14...v15) --- updated-dependencies: - dependency-name: cachix/install-nix-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-15 16:02:51 +03:00
"lastModified": 1637186689,
"narHash": "sha256-NU7BhgnwA/3ibmCeSzFK6xGi+Bari9mPfn+4cBmyEjw=",
Update flake.lock Stupid nix decided to make this a path instead, because by default the nixpkgs registry item is broken
2020-10-23 23:33:16 +03:00
"owner": "NixOS",
"repo": "nixpkgs",
Bump cachix/install-nix-action from 14 to 15 Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 14 to 15. - [Release notes](https://github.com/cachix/install-nix-action/releases) - [Commits](https://github.com/cachix/install-nix-action/compare/v14...v15) --- updated-dependencies: - dependency-name: cachix/install-nix-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-15 16:02:51 +03:00
"rev": "7fad01d9d5a3f82081c00fb57918d64145dc904c",
Update flake.lock Stupid nix decided to make this a path instead, because by default the nixpkgs registry item is broken
2020-10-23 23:33:16 +03:00
"type": "github"
Create flake.nix
2020-10-23 17:48:17 +03:00
},
"original": {
bump nixpkgs also make branch explicit, otherwise updates depends on user's /etc/nix/registry.json
2021-02-10 11:00:13 +03:00
"owner": "NixOS",
"ref": "nixpkgs-unstable",
"repo": "nixpkgs",
"type": "github"
Create flake.nix
2020-10-23 17:48:17 +03:00
}
},
"root": {
"inputs": {
For module-only consumers, avoid depending on nixpkgs This seems odd, but it works since input dependencies are lazily fetched that means a downstream repo, that only consumes the modules output (like for example `divnix/digga`), does never fetch nor instantiate nixpkgs proper (which would be costly). This enables `divnix/digga` to continue to _not_ depend on `nixpkgs` for operation. (it still depends on `nixpkgs` as a strict development dependency, but beacause of the black magic which I describe above, no end user will ever fetch it's depenency on `nixpkgs`. So, here, we want to implement a similar trick to avoid acquireing deps where they should net be acquired.
2021-06-17 02:00:15 +03:00
"nixlib": "nixlib",
Create flake.nix
2020-10-23 17:48:17 +03:00
"nixpkgs": "nixpkgs"
}
}
},
"root": "root",
"version": 7
}
Reference in New Issue Copy Permalink