| 20 May 2023 |
 Charles | personally i was kind of imagining a reference-style thing where there's a Q&A matrix and then based on your answers you can get directed to a section explaining how to install a package given your answers to the question | 22:24:22 |
| Charles | questions including things like "are you on nixos", "is it in nixpkgs", "are you using flakes", "do you want it installed globally or for your user only", "do you want it installed permanently or just to use it temporarily", etc | 22:25:12 |
| Charles | * personally i was kind of imagining a reference-style thing where there's a Q&A matrix and then based on your answers you can get directed to a section explaining how to install a package given your answers to the questions | 22:26:10 |
| Charles | * questions including things like "are you on nixos", "is it in nixpkgs", "are you using flakes", "do you want it installed globally (configuration.nix), for your user only (home-manager), or in a specific project environment only (shell.nix)", "do you want it installed permanently (declarative) or just to use it temporarily (nix-shell)", etc | 22:27:46 |
| Charles | (i don't have particularly strong feelings as to exactly how this information is presented, i'm just throwing some ideas around) | 22:30:13 |
| 21 May 2023 |
 asymmetric | does anyone understand sphinx? i'd like to add a link to the footer on nix.dev, but i can't find a way to do that. apparently i have to override the footer block in the default layout, but when i do, my HTML doesn't end up in the footer element | 16:42:09 |
| 22 May 2023 |
 @zmitchell:matrix.org | I’ll take a look, sometimes that kind of config is in conf.py at the top level of the repo | 12:33:25 |
| 23 May 2023 |
 j-k | We have release notes for nixos but we don't really have anything for nixpkgs itself, has this been raised before?
buildFHSEnv moving from the chroot version to bubblewrap has broken a couple things and will be pretty much invisible to people updating to 23.05. There's a comment in all-packages.nix but that's not particularly visible
https://github.com/NixOS/nixpkgs/pull/225748 | 13:30:31 |
 raitobezarius |
We have release notes for nixos but we don't really have anything for nixpkgs itself, has this been raised before?
it's really the nixos releases usually
| 13:31:13 |
| raitobezarius | this has been raised before by multiple contributors | 13:31:21 |
 wiseh | Minijackson I found this, in case it might help you! https://vi.stackexchange.com/questions/2846/how-to-set-up-vim-to-work-with-one-sentence-per-line | 17:15:01 |
 Minijackson | ooooh, thanks a lot! I'll certainly try this ^^ | 17:15:39 |
| 25 May 2023 |
| asymmetric | I won’t be able to attend today, sorry! | 13:00:30 |
| raitobezarius changed their display name from raitobezarius to disko in NixOS 23.11 when. | 13:32:21 |
| raitobezarius changed their display name from disko in NixOS 23.11 when to raitobezarius. | 13:37:27 |
| 26 May 2023 |
 pennae | zmitchellfricklerhandwerk: do we have any feedback about keeping/dropping the epub export (temporarily) yet? | 15:07:25 |
 infinisil | In reply to @pennae:matrix.eno.space
zmitchellfricklerhandwerk: do we have any feedback about keeping/dropping the epub export (temporarily) yet? How about we change the epub to be just a single page telling users that it's deprecated and linking to the html manual instead. Also to report it in an issue if somebody depends on epub. | 15:42:26 |
| pennae | we can do that. all we need is a decision which way to go | 15:43:06 |
| infinisil | If we don't have any feedback to epub, I think that idea is what we should do. In particular now that the release is branched off, so users have lots of time to report that they need epub until the next release | 15:44:20 |
| pennae | if anyone wants to implement epub export in nixos-render-docs before that (jan tojnar offered i think) we can keep it too | 15:44:23 |
| infinisil | The epub feels like baggage we don't really have the resources to maintain, so I'd rather drop it until we have a significant user base that needs it | 15:45:11 |
| infinisil | * The epub feels like baggage we don't really have the resources to maintain, so I'd rather drop it unless we have a significant user base that needs it | 15:45:20 |
| pennae | keeping docbook around to produce a placeholder epub that only as a link and a deprecation notice is just so ironic | 15:48:06 |
| pennae | but that's fine too. we're just not going to start moving properly on the nixpkgs manual conversion and removing docbook from the nixos manual completely until this is fixed. maybe we should have a vote or something | 15:49:14 |
| infinisil | pennae: It's effectively a constant document at that point, so docbook generation wouldn't even be necessary anymore, I'd be fine with it just being a rendered epub hosted somewhere that we just pkgs.fetch* :P | 16:13:11 |
| pennae | nixos/doc/epub/is-deprecated.epub | 16:14:13 |
| pennae | sure, also fine. amounts to dumping a blob into git which doesn't feel too nice, but it's small enough vs the rest of nixpkgs to not matter :) | 16:14:54 |
| infinisil | Oh yeah that sounds good too 😆 | 16:15:24 |
| pennae | nixos manual could drop docbook today if we (even just temporarily) deprecate docbook, nixpkgs manual is a bit out but shouldn't be by too much. we've experimented in the past and got the manual to render, but haven't checked for content equality and it's been a few months now too | 16:20:43 |
 joepie91 🏳️🌈 | https://nixos.org/learn.html is broken again, in the same way as quite some time ago | 22:15:38 |
