In reply to @pennae:matrix.eno.space
set by the flake machinery because it's a git repo, probably

Hm no, at least I don't see how a flake would do that. An empty flake like this:

{
  outputs = { self, ... }: {
    foo = self;
  };
}

called with nix eval .#foo doesn't show a rev attribute.

In reply to @pennae:matrix.eno.space
set by the flake machinery because it's a git repo, probably

Hm no, at least I don't see how a flake would do that. An empty flake in a Git repo, like this:

{
  outputs = { self, ... }: {
    foo = self;
  };
}

called with nix eval .#foo doesn't show a rev attribute.

There is more Nix nature in one line of Nix language than in ten thousand lines of C++

https://www.catb.org/esr/writings/unix-koans/ten-thousand.html

In reply to @fricklerhandwerk:matrix.org

There is a wealth of information here: https://nixos.wiki/wiki/C

Mostly written by @Mic92 in past years AFAIK. Would be great to have that closer to the code, because all of that is Nixpkgs material.

We still haven't really figured out how to organise troubleshooting tips and other guide-like material across the ecosystem though. The last state of affairs was that we converged on the idea that it should be a bit like what Johannes Kirschbauer @hsjobeki proposes for function documentation, but for guides: have a uniform format used across Nix, Nixpkgs, and NixOS, and present that in one place, annotated with tags and searchable. But that is a lot of "should", and will require thinking about the structure of the manuals, and moving around lots of text.

In reply to @fricklerhandwerk:matrix.org

Those were recently improved:

• https://github.com/NixOS/nixpkgs/pull/280592
• https://github.com/NixOS/nixpkgs/pull/277534

But there's definitely still work to do. Ideally we'd also render that stuff directly from the source. At least there is no duplication any more. I can imagine danielsidhion could help with reviews.

In reply to @rina/:matrix.org
there is documentation in the source, so maybe it's an issue of making them render in the manual? not sure

In reply to @rina/:matrix.org
there is documentation in the source, so maybe it's an issue of making them render in the manual? not sure

In reply to @rina/:matrix.org
there is documentation in the source, so maybe it's an issue of making them render in the manual? not sure

In reply to @infinisil:matrix.org
I'd also favor having it in the source code, but not having duplicated docs is more important than that

In reply to @infinisil:matrix.org
I'd also favor having it in the source code, but not having duplicated docs is more important than that

I'd like moving those back into the source code until we have a working system that allows to track external documents, so we dont loose track of the reference documentation.

More importantly we should work on reference tracking for those that are moved already. Maybe i'll open a PR soonish.

I'd like moving those back into the source code until we have a working system that allows to track external documents, so we dont loose track of the reference documentation.

More importantly we should work on reference tracking for those that are moved already. Maybe i'll open a PR with a proposed solution soonish.