| 1 Jan 2024 |
|  mjolnir banned  @themountainking:matrix.org (ban evasion). | 02:20:14 |
| 2 Jan 2024 |
|  gli.al changed their display name from gli.al ☎️ 9402 to gli.al. | 16:34:11 |
| 3 Jan 2024 |
 Bryan | In reply to @themountainking:matrix.org
Could you please explain why your way is more beneficial? I'd like to understand your viewpoint. I'm sorry - I missed this.
I am not so worried about application distribution as consumption and profiles with a declarative source and reusable dependencies seem preferable there. Distributors have different priorities (even leading some to recently only support shipping their applications as flatpaks!, but the idea that the consumer must accept what the distributor gives them is toxic and limiting. I'm happy to have alternatives and willing to learn from flatpaks - I just see their "realm" as slightly more limited than nix's (though nix's does have limitations and shortcomings as well)
| 17:50:11 |
| 4 Jan 2024 |
|  eahlberg joined the room. | 14:54:55 |
| 5 Jan 2024 |
|  @avhb:matrix.org joined the room. | 12:55:19 |
| 7 Jan 2024 |
|  samasaur joined the room. | 13:50:51 |
|  @losh:matrix.cert.ccc.de joined the room. | 18:50:45 |
| 8 Jan 2024 |
|  stupidcomputer joined the room. | 04:37:44 |
| stupidcomputer | hey, anyone on? | 04:37:53 |
 tomberek | possibly | 04:48:26 |
|  Oro (any/all) changed their display name from Rika (she/her) to Oro (they/she). | 09:17:46 |
| Oro (any/all) changed their profile picture. | 09:19:00 |
| 9 Jan 2024 |
|  @andar1an:matrix.org joined the room. | 20:29:03 |
| 11 Jan 2024 |
| @andar1an:matrix.org left the room. | 11:43:31 |
| 12 Jan 2024 |
 lxsameer | hey folks, is there any way to patch nixpkgs itself and then use it as an input in flakes? | 19:00:32 |
| samasaur | You can maintain a fork of nixpkgs and use that as a flake input | 19:05:22 |
| samasaur | I’m not sure if there’s a way to say “take the latest nixpkgs on some channel, apply a patch, and use that as a flake input” | 19:05:55 |
| lxsameer | In reply to @samasaur:matrix.org
You can maintain a fork of nixpkgs and use that as a flake input I was hoping not to do that | 19:07:10 |
 mewp | just to be sure: overlays do not solve your problem? | 22:02:22 |
| 13 Jan 2024 |
 @aidalgol:matrix.org | The Nix developers are still trying to figure out how to support this cleanly. https://github.com/NixOS/nix/issues/3920 | 03:10:02 |
| lxsameer | In reply to @mewp:nurupo.pl
just to be sure: overlays do not solve your problem? no, I need to patch nixpkgs itself, not the packages it contains | 12:16:25 |
| lxsameer | In reply to @aidalgol:matrix.org
The Nix developers are still trying to figure out how to support this cleanly. https://github.com/NixOS/nix/issues/3920 this is pretty cool | 12:17:25 |
|  rolfst changed their display name from Rolf Strijdhorst to rolfst. | 16:03:43 |
|  felipeggmarcelino joined the room. | 19:53:24 |
| 15 Jan 2024 |
|  @virtu:matrix.im left the room. | 13:44:25 |
| 16 Jan 2024 |
|  fsagbuya changed their profile picture. | 05:54:14 |
| lxsameer | hey folks, do you have a development workflow using flakes? if you do, would you mind telling me about it? I need these data for a talk | 16:22:23 |
|  @NobbZ:matrix.org left the room. | 19:30:32 |
| 17 Jan 2024 |
| tomberek | That's a broad topic. But yes. I tend to start as basic as possible. At first it can be fairly self-contained. Making devShells and packages for a project provides a good sanity check that you really understand what goes into the development process. Then comes CI, with its own complication and integrations. The hardest part is often when trying to have multiple projects that interact. At this point it can get complicated with topics like overlays, monorepos, flakebumps, overrides, follows. Reach out if you have q's. | 00:11:22 |
| lxsameer | cool, few question: 1) what do you use on the CI? 2) how do you manage inter project dependencies and flake bumps | 13:14:31 |
