Robert Hensing

Do we even want releases? I'd be ok with "rolling" releases via `github:NixOS/flake-compat` personally. It would just make people would for stuff to be tagged; seems counterproductive.

I have removed the tags, because they caused a wrong impression that this repo did serious release management. I can restore them if that's a problem for more than a...

No hard feelings; this just isn't the right project for it. - https://github.com/NixOS/flake-compat/pull/85

Seems reasonable, and I like that this is a simplification. `isShallow` and its usage were introduced in https://github.com/NixOS/flake-compat/commit/2c2a50af4dd77d8457284301b521448289b5a3ed without explanation why `isShallow` would have been a prerequisite for validity. Shallow...

Yes, it is about the overall state of the projects, but I do believe it affects our ability to reason about inputs due to most of it being centered around...

Some prior art is https://github.com/NixOS/nix/pull/11952, but if flake-compat finds a more general way, e.g. allowing arbitrary flake by value, I think that'd be preferable.

A "flake" can be refer to potentially many things 1. a source tree 2. a source tree and a closure of flake inputs 3. an entry in `inputs` 4. the...

I've rebased and put my suggestion for a changelog entry in the PR description, because it kept causing conflicts. Let us know if there's anything else we can do!

Sitemap purpose: Tell search engines "here are all the pages that exist at this location" Canonical purpose: Tell search engines "if you found this page, the authoritative version is at...

@limwa Nix restricts flake `inputs` to a subset of the language that does not permit that. I'll add https://github.com/NixOS/rfcs/pull/193#discussion_r2596709067 to address this.