 | Nix Documentation | 435 Members |
| Discussion about documentation improvements around the Nix ecosystem | 91 Servers |
| Nix Documentation | 435 Members |
| Discussion about documentation improvements around the Nix ecosystem | 91 Servers |
| Sender | Message | Time |
|---|---|---|
| 17 Jul 2023 | ||
 John Ericson | :) | 18:36:50 |
| John Ericson | <3 | 18:36:55 |
 asymmetric | the corollary is that once they're stabilized, we should imo just go ahead and document them on nix.dev, even though some of us will still disagree with them on a design level | 18:37:53 |
| asymmetric | * the corollary is that once (if!) they're stabilized, we should imo just go ahead and document them on nix.dev, even though some of us will still disagree with them on a design level | 18:38:17 |
 @brian:bmcgee.ie | In reply to @infinisil:matrix.orgI like the idea of a stripped down nix core with things like flakes becoming a different frontend. | 18:38:39 |
| @brian:bmcgee.ie | It would allow for faster iteration in different areas too since you've broken out the use cases. Getting the core right is gonna be the tricky part | 18:42:09 |
 infinisil | I have an RFC draft that if accepted would be a really big step towards that | 18:43:30 |
| @brian:bmcgee.ie | Link please | 18:44:04 |
| @brian:bmcgee.ie | If it's up sonewhere | 18:44:21 |
| @brian:bmcgee.ie | * If it's up somewhere | 18:44:28 |
| infinisil | It's really draft right now, but because I don't have a lot of time to work on it right now I'm sharing it in the hopes of others being able to help out with it, PR's and issues appreciated: https://github.com/tweag/epcb | 18:44:28 |
| infinisil | Well, it's a mess of old and new drafts, don't read it too closely, but feel free to ask me questions if confused | 18:46:25 |
| infinisil | Btw this is using the repository-as-RFC approach proposed in https://github.com/NixOS/rfcs/pull/138 | 18:47:27 |
 raitobezarius | In reply to @brian:bmcgee.ie Just to provide another datapoint: I have spent my last years removing Flakes from project (latest example in mind is bcachefs with an impossible Flake setup…), dealing with people who tries to shoehorn Flakes into the wrong project because it is not fit for it, dealing with a lot of kind of footguns generated by deep dependency management brought by Flakes, etc. While I do understand the value of Flakes and use them sparringly or have projects with them, I am not excited to see documentation team having to focus on that, especially given that most people does not know how to do things the vanilla way (sometimes people do say the "legacy" which irks me the wrong way, because Flakes does not supplement the vanilla usecases yet, for example, try to repair your remote store with the "nix-command" CLI :)) | 19:10:16 |
 @nerves:bark.lgbt joined the room. | 20:29:45 | |
| infinisil | Would like to have some opinions on this: https://github.com/NixOS/nixpkgs/issues/244056 | 21:36:53 |
| 18 Jul 2023 | ||
 nbp | From my point of view, is was kind of part of it, as this was the natural evolution of extending Nixpkgs with a new set of packages. This point was probably more true before the addition of overlays … :/ | 14:42:53 |
| nbp | * infinisil: From my point of view, is was kind of part of it, as this was the natural evolution of extending Nixpkgs with a new set of packages. This point was probably more true before the addition of overlays … :/ | 14:43:18 |
| nbp | Maybe a work-around would be to index the Markdown files, saying that the everything related to submitting patches upstream, in Nixpkgs, would be describe in a set of files which are part of the distributed sources. | 14:44:44 |
 mikecm joined the room. | 15:39:24 | |
| infinisil | proofconstruction: Interesting coincidence: https://www.reddit.com/r/NixOS/comments/1531nyc/installing_nixos_on_raspberry_pi_4/, in that blog post GUI works, but they're using an older NixOS version. There's also an appendix that links to failed attempts. Maybe you could contact the author to work together on improving the nix.dev tutorial for that even more (ideally encourage them to contribute the docs upstream) | 20:59:53 |
 proofconstruction | In reply to @infinisil:matrix.orgI have already been in contact with this person since last week, and have of course encouraged contribution upstream 🙂 | 21:00:52 |
| proofconstruction | Seems that there's some relatively recent issue in nixos-hardware which is preventing X11 rendering. I have very little time to chase after that, though, and no personal interest: my pi4 is a headless router. We discussed this briefly in a previous meeting, but unless someone wanted to own this documentation (and really, it should be whoever is working on rpi support in nixos-hardware), I would actually prefer to just remove the existing tutorial and let people find the wiki page, or the post by that user, etc | 21:05:18 |
| infinisil | proofconstruction: Sounds good! | 21:07:09 |
| 20 Jul 2023 | ||
 alejandrosame | I won't be able to join today's meeting. | 04:59:02 |
| @brian:bmcgee.ie | Can't make it today, just got pulled into a client call | 12:29:12 |
| proofconstruction | Me either for the LJWG. Only update is PR #650 in progress, making edits based on @fricklerhandwerk's review and will have them pushed before tomorrow. Feel free to add comments to that one. In particular I'd like to have one or two more packages to write increasingly complex derivations for, to demonstrate things like NIX_LD_PATH and pkg-config includes. I also don't have a good story for how to determine where a dependency lives (in the tutorial, we need X11/Xlib.h from xorg.libX11.dev but I don't know a nice way to actually find these things beyond googling and knowing something about packaging conventions in other projects. Suggestions welcome | 13:12:19 |
 Rígille S. B. Menezes joined the room. | 17:14:12 | |
| infinisil | pennae: asymmetric: I fixed the line indentation bug in nixdoc :D https://github.com/nix-community/nixdoc/pull/62 | 18:33:18 |
 pennae | In reply to @infinisil:matrix.orgit looks like you reinvented textwrap::dedent? | 18:44:50 |