flakes: clarify flake-compat/flake-inputs#1209
flakes: clarify flake-compat/flake-inputs#1209KiaraGrouwstra wants to merge 1 commit intoNixOS:masterfrom
Conversation
Update the /concepts/flakes page to note flake-compat and flake-inputs both work from the publisher's as well as the consumer's perspective. Note that while flake-compat is documented better, flake-compat seems to still [lack support for overrides](https://git.lix.systems/lix-project/flake-compat/issues/82). Signed-off-by: cinereal <cinereal@riseup.net>
|
CI complains 429 (Too Many Requests) |
| - Handle dependencies inline using functions such as the [fetchers] or [`builtins.fetchTree`]. | ||
|
|
||
| [fetchers]: https://nixos.org/manual/nixpkgs/stable/#chap-pkgs-fetchers | ||
| [`flake-inputs`]: https://github.com/fricklerhandwerk/flake-inputs |
There was a problem hiding this comment.
I don't think this should be advertised here. I'm not actively maintaining it, and IMO the Lix fork is better in multiple regards:
- the diff to nixos/flake-compat is more obvious (this was not a goal for my hack, but is relevant when using forks)
- it has tests
- it can turn off local path copying (because my diff is arbitrary large, it's too much of a hassle for me right now to adopt the patch)
There was a problem hiding this comment.
i initially intended to supersede flake-inputs by flake-compat here, yeah - it's only when i realized flake-compat isn't fully superior yet (see above) that i considered to instead mention both still.
i mentioned them about your approach there, so hopefully as they address that we can just leave out mention of flake-inputs here.
|
@KiaraGrouwstra What is the state of this PR? I think we should simply drop the reference to "flake-inputs" ? |
|
technically pending on review of https://git.lix.systems/lix-project/flake-compat/pulls/87 (if not also https://git.lix.systems/lix-project/flake-compat/issues/85) |
3 participants
Update the /concepts/flakes page to note flake-compat and flake-inputs both work from the publisher's as well as the consumer's perspective.
Note that while flake-compat is documented better, flake-compat seems to still lack support for
overrides.