| 26 Jul 2024 |
Philip Taron (UTC-8) | fricklerhandwerk: regarding your comment, note that doc/default.nix and doc/shell.nix remain: the guts of how they're implemented move over. | 17:11:14 |
Philip Taron (UTC-8) | I think that's the way it ought to be. | 17:11:25 |
Sandro 🐧 | like nixos-install-tools and tests.nixos-functions.nixos-test already do | 17:11:45 |
fricklerhandwerk | In reply to @philiptaron:matrix.org fricklerhandwerk: regarding your comment, note that doc/default.nix and doc/shell.nix remain: the guts of how they're implemented move over. I understand, and splitting that into two parts doesn't make much sense to me. I suggest not breaking locality | 17:12:10 |
Philip Taron (UTC-8) | Hmmm, I really liked how doc/ was now the actual documentation and there wasn't what I considered to be an awkward doc-support directory that wasn't documentation. But I'll take your feedback. | 17:14:31 |
fricklerhandwerk | In reply to @philiptaron:matrix.org Hmmm, I really liked how doc/ was now the actual documentation and there wasn't what I considered to be an awkward doc-support directory that wasn't documentation. But I'll take your feedback. I understand, but arguably none of that content should actually live in there, and instead be right in or next to the code it's documenting | 17:18:56 |
fricklerhandwerk | And also the glue code is hardly separable from the content structure that it helps produce | 17:19:24 |
fricklerhandwerk | In reply to @philiptaron:matrix.org Hmmm, I really liked how doc/ was now the actual documentation and there wasn't what I considered to be an awkward doc-support directory that wasn't documentation. But I'll take your feedback. * I understand, but arguably most of that content should actually live in there, and instead be right in or next to the code it's documenting | 17:19:39 |
fricklerhandwerk | * I understand, but arguably barely any of that content should actually live in there, and instead be right in or next to the code it's documenting | 17:19:47 |
@johannes.kirschbauer:scs.ems.host | Yeah good work appreciate it.
I also agree to the locality point of fricklerhandwerk | 17:22:47 |
@johannes.kirschbauer:scs.ems.host | But also could be another PR | 17:22:59 |
fricklerhandwerk | In reply to @johannes.kirschbauer:scs.ems.host But also could be another PR Sure, moving around lots of stuff is a completely different thing. I'm just saying let's leave everything there, but make the package more conventional | 17:24:21 |
Philip Taron (UTC-8) | In reply to @fricklerhandwerk:matrix.org And also the glue code is hardly separable from the content structure that it helps produce I think I have the opposite intuition -- most of nixpkgs is code to orchestrate builds that is separated from the origin (i.e. upstream.) So when there's orchestration of builds within nixpkgs, my intuition is that separating it is normal and expected.
Since nixpkgs building on nixpkgs is a rare occurrence (mostly maintainers/, doc/, and nixos/) I doubt there's a pattern to it.
I'll follow your guidance, though.
| 17:26:42 |
Philip Taron (UTC-8) | https://github.com/NixOS/nixpkgs/pull/311459 -- I think it's ready for review. | 20:52:24 |
| 28 Jul 2024 |
| matthewcroughan changed their display name from matthewcroughan to matthewcroughan - going to nix.camp. | 16:06:59 |
| 29 Jul 2024 |
| @imincik:matrix.org left the room. | 10:01:46 |
| 6 Aug 2024 |
| likivik joined the room. | 00:01:15 |
| 8 Aug 2024 |
| Alyssa Ross set a profile picture. | 18:48:35 |
| 10 Aug 2024 |
| Austin Horstman changed their display name from Khaneliman to Austin Horstman. | 03:50:06 |
| 11 Aug 2024 |
toraritte | hey, are there any active work going on the Nixpkgs manual's overrides and overlays sections? I only found https://github.com/NixOS/nixpkgs/pull/255132 (doc: Improve overlays section) on the documentation team's project board (https://github.com/orgs/NixOS/projects/15/views/1) | 01:29:42 |
infinisil | In reply to @metello:matrix.org hey, are there any active work going on the Nixpkgs manual's overrides and overlays sections? I only found https://github.com/NixOS/nixpkgs/pull/255132 (doc: Improve overlays section) on the documentation team's project board (https://github.com/orgs/NixOS/projects/15/views/1) Related ongoing work by Johannes Kirschbauer @hsjobeki: https://github.com/NixOS/nixpkgs/pull/325479 | 15:24:25 |
@johannes.kirschbauer:scs.ems.host | Is there some section that explains what nixpkgs is and how it works. By that i mean - How is nixpgs bootstrapped, what are packageSets, scopes and why can packageA use packageB as buildInput if they are defined in the same package set. (fixed point recursion) | 15:47:15 |
infinisil | I don't think so | 16:12:03 |
infinisil | Notably what Nixpkgs is should be in the Nixpkgs manual, while how it works should arguably be in the contribution docs | 16:12:30 |
| 17 Aug 2024 |
| isabel joined the room. | 12:43:50 |
| 19 Aug 2024 |
| alejandrosame left the room. | 08:51:38 |
| alejandrosame joined the room. | 08:54:02 |
| cafkafk changed their profile picture. | 12:45:38 |
@johannes.kirschbauer:scs.ems.host | Asking this Here because i Cannot figure it Out by Reading our Docs;
Anyone knows how impureEnvVars Work?
I have found this one. But i dont Like to write credentials into my nixos config.
https://discourse.nixos.org/t/how-to-use-impureenvvars/30322
Can i make 'nix build' Pickup/Forward the impureEnvVars somehow?
| 15:52:35 |
| 20 Aug 2024 |
| @benjaminedwardwebb:envs.net changed their display name from benjaminedwardwebb to benwebb. | 12:44:14 |