nix-community/dream2nix
1
1
Fork 0
mirror of https://github.com/nix-community/dream2nix.git synced 2024-12-23 22:48:02 +03:00
Code Issues Projects Releases Wiki Activity
3fc4a2ad97
dream2nix/flake.lock

89 lines
2.2 KiB
Plaintext
Raw Normal View History

implement UI and examples: - generic translator CLI exposed as flake app - flake app 'install' to install the framework - generic fetcher - simple translator for python - simple builer for python
2021-09-10 00:42:56 +03:00
{
"nodes": {
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"nixpkgs": {
formatting: add flake apps + prepare hooks
2022-03-07 09:57:22 +03:00
"locked": {
update nixpkgs
2023-12-12 08:54:55 +03:00
"lastModified": 1702272962,
"narHash": "sha256-D+zHwkwPc6oYQ4G3A1HuadopqRwUY/JkMwHz1YF7j4Q=",
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"owner": "NixOS",
"repo": "nixpkgs",
update nixpkgs
2023-12-12 08:54:55 +03:00
"rev": "e97b3e4186bcadf0ef1b6be22b8558eab1cdeb5d",
formatting: add flake apps + prepare hooks
2022-03-07 09:57:22 +03:00
"type": "github"
},
"original": {
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"owner": "NixOS",
"ref": "nixpkgs-unstable",
"repo": "nixpkgs",
formatting: add flake apps + prepare hooks
2022-03-07 09:57:22 +03:00
"type": "github"
}
},
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"purescript-overlay": {
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
"inputs": {
"nixpkgs": [
"nixpkgs"
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
],
"slimlock": "slimlock"
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
},
"locked": {
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"lastModified": 1696022621,
"narHash": "sha256-eMjFmsj2G1E0Q5XiibUNgFjTiSz0GxIeSSzzVdoN730=",
"owner": "thomashoneyman",
"repo": "purescript-overlay",
"rev": "047c7933abd6da8aa239904422e22d190ce55ead",
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
"type": "github"
},
"original": {
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"owner": "thomashoneyman",
"repo": "purescript-overlay",
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
"type": "github"
}
},
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"pyproject-nix": {
"flake": false,
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
"locked": {
pyproject.nix: switch to dream2nix fork ... until the open PRs are merged
2023-12-13 09:23:44 +03:00
"lastModified": 1702448246,
"narHash": "sha256-hFg5s/hoJFv7tDpiGvEvXP0UfFvFEDgTdyHIjDVHu1I=",
"owner": "davhau",
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"repo": "pyproject.nix",
pyproject.nix: switch to dream2nix fork ... until the open PRs are merged
2023-12-13 09:23:44 +03:00
"rev": "5a06a2697b228c04dd2f35659b4b659ca74f7aeb",
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
"type": "github"
},
"original": {
pyproject.nix: switch to dream2nix fork ... until the open PRs are merged
2023-12-13 09:23:44 +03:00
"owner": "davhau",
"ref": "dream2nix",
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"repo": "pyproject.nix",
formatting: add flake apps + prepare hooks
2022-03-07 09:57:22 +03:00
"type": "github"
}
},
implement UI and examples: - generic translator CLI exposed as flake app - flake app 'install' to install the framework - generic fetcher - simple translator for python - simple builer for python
2021-09-10 00:42:56 +03:00
"root": {
"inputs": {
add translator: npmlock2nix
2021-09-14 05:00:29 +03:00
"nixpkgs": "nixpkgs",
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"purescript-overlay": "purescript-overlay",
"pyproject-nix": "pyproject-nix"
implement UI and examples: - generic translator CLI exposed as flake app - flake app 'install' to install the framework - generic fetcher - simple translator for python - simple builer for python
2021-09-10 00:42:56 +03:00
}
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
},
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"slimlock": {
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
"inputs": {
"nixpkgs": [
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"purescript-overlay",
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
"nixpkgs"
]
},
"locked": {
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"lastModified": 1688610262,
"narHash": "sha256-Wg0ViDotFWGWqKIQzyYCgayeH8s4U1OZcTiWTQYdAp4=",
"owner": "thomashoneyman",
"repo": "slimlock",
"rev": "b5c6cdcaf636ebbebd0a1f32520929394493f1a6",
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
"type": "github"
},
"original": {
refactor: move dev related things to /dev-flake The goal is to reduce the flake inputs visible to the user Still, the top-level flake re-exposes the outputs of the dev-flake, but without exposing its inputs. This means a devShell is still available in the top-level, for example. This also removes the /modules/flake.nix. Its original purpose was separating the modules inputs from the development inputs, but this is now done the opposite way around by moving the dev inputs to /dev-flake/flake.nix.
2023-11-01 19:54:06 +03:00
"owner": "thomashoneyman",
"repo": "slimlock",
tests: add nix unit tests for pip module
2023-08-28 17:47:15 +03:00
"type": "github"
}
implement UI and examples: - generic translator CLI exposed as flake app - flake app 'install' to install the framework - generic fetcher - simple translator for python - simple builer for python
2021-09-10 00:42:56 +03:00
}
},
"root": "root",
"version": 7
}
Reference in New Issue Copy Permalink