!avYyleMexqjFHoqrME:nixos.org

Nix Documentation

419 Members
Discussion about documentation improvements around the Nix ecosystem83 Servers

Load older messages


SenderMessageTime
15 Oct 2023
@jade_:matrix.org@jade_:matrix.org* I have a long post of feedback which tbf is mostly probably stuff we already know, sourced from a friend who just learned NixOS. Is this the right place to put it or should it go on discourse?22:04:00
@jade_:matrix.org@jade_:matrix.org

Oh, an update on me learning nix stuff and just some introspection: Since the manual is better than the wiki, the wiki is more of a hindrance than an advantage because it's outdated. I'd honestly prefer the manual to be the default result when i google something (but that needs some cute SEO).

(jade): it sucks that our manual is incredibly anti seo because the fact that it's one massive page is incredibly nice to ctrl f and not have to trust some terrible in-page search engine. but the upgrade ryantm is doing would help here i think.

The manual is a nice resource for certain things especially initial setup, but there's a lack of (readily accessible) resources to do customisations like adding nvim plugins, etc. I understand that it's just adding config files like normal distros now.. But that brings up a suggestion of being more clear about the NixOS philosophy. I get that it's highly reproducible, but what exactly is reproducible. What are the things I should aim to replicate with my configurations (is it just my packages and development environments?, or does it also include my shell and text editor configuration? Are my flatpak apps supposed be included in this reproducible build for best practices? how am i supposed to even go about doing this?). While I get that it's honestly up to you, I would highly prefer a guide on how to set up my OS with best practices or really avoid bad practices like nix-env -i

Also the obvious thing remains obvious in terms of documentation missing really explaining what a flake is? I got it at the end, but wow it took me a while. The communication of flakes seems like it's to a systems expert rather than someone who has intermediate or novice skills with sysmgmt.

(jade): especially it's hard to find it in the nix manual and we're doing no favours by having our manuals all separated so that you can't search in one to find things in the other. global search across nix.dev, nix, nixpkgs, and nixos docs would be good maybe?

But also the community is really good like I found this really useful guide which I don't know if you already know which does a good job imo: https://nixos-and-flakes.thiscute.world/ (it's not perfect, but does a good job nonetheless)

22:09:55
17 Oct 2023
@ryantm:matrix.orgryantmI'm planning to merge this in one week unless I get feedback about it. https://github.com/NixOS/nixpkgs/pull/108063/files it's a fairly self contained change.13:20:48
@artturin:matrix.orgArtturin
In reply to @ryantm:matrix.org
I'm planning to merge this in one week unless I get feedback about it. https://github.com/NixOS/nixpkgs/pull/108063/files it's a fairly self contained change.
Doesn't seem that it's been linked to from https://github.com/NixOS/nixpkgs/issues/156309
It's not mdbook but it's about creating a paged docs
16:49:24
19 Oct 2023
@fricklerhandwerk:matrix.orgfricklerhandwerkI'm likely not going to make it to the meeting today. If there is anything anyone really needs to discuss or review or get merged today, please ping me and I will try to arrange it regardless.08:14:57
@infinisil:matrix.orginfinisil Today me and henrik-ch started curating the doc team member list: https://discourse.nixos.org/t/2023-10-19-documentation-team-meeting-notes-87/34349 14:55:27
@infinisil:matrix.orginfinisil henrik-ch: See the edit history of the meeting notes, did minor updates 14:58:14
20 Oct 2023
@zmitchell:matrix.org@zmitchell:matrix.orgI finally have a PR up for sphinxext-rediraffe: https://github.com/NixOS/nixpkgs/pull/26218204:38:16
@ninjatrappeur:alternativebit.fr@ninjatrappeur:alternativebit.fr changed their display name from NinjaTrappeur to PicNoir (was Ninjatrappeur).10:34:34
@ckie:ckie.devmei ๐ŸŒ’& hey so the docs for fixed-output derivations don't have any direct mention of the fact they enable network access? only implications with the fetchurl example? 19:33:33
@ckie:ckie.devmei ๐ŸŒ’&and that regular derivations don't, at least when the sandbox is enabled which I think is basically always?19:35:38
21 Oct 2023
@fricklerhandwerk:matrix.orgfricklerhandwerk
In reply to @ckie:ckie.dev
hey so the docs for fixed-output derivations don't have any direct mention of the fact they enable network access? only implications with the fetchurl example?
Yes, apparently. Would you mind adding a sentence that mentions this?
09:52:09
@fricklerhandwerk:matrix.orgfricklerhandwerk

If you need some guidance to make the change, check this new page: https://nixos.org/manual/nix/unstable/contributing/documentation

It likely wonโ€™t cover everything you need, and Iโ€™d be happy about feedback on how to improve it

09:53:30
@alejandrosame:matrix.orgalejandrosameIs the team aware of this PR: https://github.com/NixOS/nixpkgs/pull/108063?14:10:41
@proofconstruction:matrix.orgproofconstructionHave been very busy but will be able to review some stuff this weekend14:32:26
@fricklerhandwerk:matrix.orgfricklerhandwerk
In reply to @alejandrosame:matrix.org
Is the team aware of this PR: https://github.com/NixOS/nixpkgs/pull/108063?
Aware but have no opinion about it.
16:20:40
22 Oct 2023
@i97henka:matrix.orghenrik-ch
In reply to @alejandrosame:matrix.org
Is the team aware of this PR: https://github.com/NixOS/nixpkgs/pull/108063?
I am aware of it - was looking at it at nixcon with ryantm .
11:29:45
@asymmetric:matrix.dapp.org.ukasymmetricis there a reason why for the module system, we say "defining an option" instead of "setting an option"? I feel like i have to think a couple seconds every time i read definition/declaration, to remember what each means. this wouldn't happen with setting/declaration15:21:40
@stefanwschroeder:matrix.orgStefan Schroeder joined the room.19:44:10
23 Oct 2023
@fricklerhandwerk:matrix.orgfricklerhandwerk
In reply to @asymmetric:matrix.dapp.org.uk
is there a reason why for the module system, we say "defining an option" instead of "setting an option"? I feel like i have to think a couple seconds every time i read definition/declaration, to remember what each means. this wouldn't happen with setting/declaration

Robert Hensing (roberth) wrote a proposal on changing that: https://github.com/NixOS/nixpkgs/issues/185234

I think it should be implemented as written. There's a pile of issues on module system docs, this is one of it.

09:41:45
@fricklerhandwerk:matrix.orgfricklerhandwerk
In reply to @asymmetric:matrix.dapp.org.uk
is there a reason why for the module system, we say "defining an option" instead of "setting an option"? I feel like i have to think a couple seconds every time i read definition/declaration, to remember what each means. this wouldn't happen with setting/declaration
*

Robert Hensing (roberth) wrote a proposal on changing that: https://github.com/NixOS/nixpkgs/issues/185234

I think it should be implemented as written. There's a pile of issues with the module system docs, this is one of it.

09:42:05
@fricklerhandwerk:matrix.orgfricklerhandwerk *

Robert Hensing (roberth) wrote a proposal on changing that: https://github.com/NixOS/nixpkgs/issues/185234

I think it should be implemented as written.

09:42:24
@fricklerhandwerk:matrix.orgfricklerhandwerkIโ€™ll only be in the meeting for the first half hour today because of a conflicting appointment11:16:47
@asymmetric:matrix.dapp.org.ukasymmetric
In reply to @fricklerhandwerk:matrix.org
Iโ€™ll only be in the meeting for the first half hour today because of a conflicting appointment
thanks! i'ld love to discuss some of this stuff on thu (i can't attend today)
12:55:00
@asymmetric:matrix.dapp.org.ukasymmetricoops, was meant as a reply to the post above ๐Ÿ˜‰12:55:11
25 Oct 2023
@federicodschonborn:matrix.org@federicodschonborn:matrix.org changed their profile picture.00:13:04
@fsbof:matrix.orgfsbofI've been upgrading NixOS. On the good side, I've had options that other distros didn't offer but I still broke stuff! Badly! I finally tracked down that "virtualisation.libvirtd.qemu.ovmf.package = pkgs.OVMFFull" updated the version of OVMF_CODE.fd which subsequently caused virtual domains using UEFI to no longer successfully boot. This is likely related to a change in size of the nvram, and starting the domains with the virsh --reset-nvram option allowed them to boot. I also needed to then go into the UEFI config and update the display resolution in order to see the actual boot process. This took hours to work through - is it worth documenting anywhere for others because I couldn't find much. Also I am still on NixOS 22.05 - Trying to get to 23.05, so my issues maybe 'out-of-date' but they got me! 10:00:05
@infinisil:matrix.orginfinisil fsbof: Sounds like that should be added (if it's not already) to the 23.05 release notes. There's a breaking changes section 10:02:31
@fsbof:matrix.orgfsbofI did look in the release notes and could only find two mentions of OVMF changes in 22.11 and 21.1110:06:09
@fsbof:matrix.orgfsbofI also managed to break it with out needing to upgrade the NixOS version - just by add the line above to configuration.nix in 22.05 when it previously didn't exist.10:08:34

Show newer messages


Back to Room ListRoom Version: 6