| 12 Jan 2024 |
 danielsidhion | Should we update https://github.com/NixOS/nixos-homepage/blob/master/scripts/update.sh to use nix flake update instead of nix flake lock then? | 16:37:51 |
 infinisil | danielsidhion: I might do that yeah | 16:39:00 |
| infinisil | (If 2.19.1 actually supports that already) | 16:39:33 |
| danielsidhion | I think it does, if the docs I'm reading are right | 16:40:20 |
| infinisil | Yeah | 16:42:32 |
| infinisil | But it doesn't support updating multiple inputs in a single command :/ | 16:43:53 |
 Chris McDonough | danielsidhion: if i could ask in context, it looks like https://github.com/NixOS/nixpkgs/pull/280520 adds an "Inputs" title... should there be a corresponding "Outputs"? | 16:45:16 |
| Chris McDonough | Or I guess "Output" heh | 16:46:36 |
| danielsidhion | Add an "output/outputs" if it makes sense. The example I put there might be somewhat bad and need rework, because I had in mind a function that outputs a derivation, so "passthru outputs" makes more sense | 16:48:58 |
| danielsidhion | For lib-style functions it might make more sense to use "output/outputs" | 16:49:34 |
| Chris McDonough | ok, i think that makes sense | 16:49:59 |
| Chris McDonough | in that trivial builders file, we have sort of haskell-style "runCommand :: String -> AttrSet -> String -> Derivation" style of documenting inputs and outputs... i'm going to remove those and go with that | 16:51:23 |
| infinisil | danielsidhion: https://github.com/NixOS/nixos-homepage/pull/1199 | 16:52:46 |
| danielsidhion | If that style of documenting inputs/outputs doesn't work well for your use case, please help improve the conventions by either adding more specific cases or helping find a common abstraction that works for more cases | 16:53:22 |
| danielsidhion | We're kind of making those conventions as I find the opportunities while working on the manual | 16:53:38 |
| Chris McDonough | yep... i don't personally think the "runCommand :: String -> AttrSet -> String -> Derivation" style is very useful so i'll replace it with what we talked about and we'l see what happens :) | 16:54:31 |
| Chris McDonough | if CI completes, could we merge https://github.com/NixOS/nixpkgs/pull/277534 as-is so far? rationale: i don't want to make more commits to it that are unrelated to the writeText* functions, which is what its about right now | 17:24:55 |
| Chris McDonough | (i'd like to make more changes to it that are related to function argument styles) | 17:25:15 |
| Chris McDonough | (but that are not related to writeText* funcs) | 17:25:46 |
| danielsidhion | I'm reviewing the pr right now | 17:33:26 |
 @jade_:matrix.org | In reply to @asymmetric:matrix.dapp.org.uk
i think we would really benefit from this. it would make it easier for people to contribute across the different projects on the platform, create links when appropriate, etc etc there's a bunch of efforts of unclear relation involving writing new docs builders. we really need to write down what they are and probably make a tracking issue to try to not step on our own toes. | 18:20:29 |
| infinisil | danielsidhion: Manual is now being updated again! https://nixos.org/manual/nixpkgs/unstable/ | 19:40:43 |
| infinisil | (merged the PR and manually triggered an update) | 19:40:56 |
| danielsidhion | Thank you for fixing it! | 19:41:26 |
| danielsidhion | In reply to @jade_:matrix.org
there's a bunch of efforts of unclear relation involving writing new docs builders. we really need to write down what they are and probably make a tracking issue to try to not step on our own toes. I think that's important, added this to the agenda for next meeting so it's not forgotten to be at least discussed, hopefully the issue is created during the meeting though | 19:43:53 |
 asymmetric | jade_: what projects/efforts are you thinking of? i know of nixos-render-docs (which is actually used in nixpkgs/nixos), mmdoc (which was supposed to be used, but isnt'). anything else? | 20:40:07 |
| asymmetric | relatedly, i was looking into the pr splitting the nixpkgs manual up, which uses mmdoc, and i think it should probably be re-implemented using nrd? | 20:49:44 |
| asymmetric | mainly because, afaict, nrd is the sanctioned way forward | 20:50:34 |
| @jade_:matrix.org | this one, which claims to "complete autogenerated documentation for the whole nix-ecosystem" (which is fundamentally contradictory with all the other projects ostensibly doing this but having nothing to do with it): https://github.com/nix-community/docnix | 20:53:12 |
| @jade_:matrix.org | the description of this and how it fits into the way everything is going to fit together is very fundamentally confusing | 20:53:54 |
