| 21 Feb 2023 |
 Sandro 🐧 | I was comparing it to having variables in let ins.
| 11:51:01 |
| Sandro 🐧 | Packages should expose all attrs written in the file otherwise overlays will become unnecessarily hard and right now I am completely against using it in any normal package. | 11:52:26 |
 Artturin | In reply to @sandro:supersandro.de
Packages should expose all attrs written in the file otherwise overlays will become unnecessarily hard and right now I am completely against using it in any normal package. it won't affect overlays https://github.com/NixOS/nixpkgs/pull/217243#issuecomment-1438756128 | 17:29:00 |
| Artturin | In reply to @sandro:supersandro.de
Packages should expose all attrs written in the file otherwise overlays will become unnecessarily hard and right now I am completely against using it in any normal package. * it won't affect override overlays https://github.com/NixOS/nixpkgs/pull/217243#issuecomment-1438756128 | 17:29:11 |
| Sandro 🐧 | If you are using overrideAttrs but sometimes you are constructing a new package by copying pname, version, src and patches from another package. Not exposing them by default just creates busy work and friction for downstream users. | 18:19:09 |
| 23 Feb 2023 |
|  @alejandrosame:matrix.org joined the room. | 17:54:27 |
| 27 Feb 2023 |
 infinisil | Unfortunately I won't be able to join today's meeting. Is there something somebody wanted to discuss today? If so, feel free to still have the meeting, but let me know beforehand so I can set up the live-stream/recording. Ping Robert Hensing (roberth) John Ericson growpotkin ( Alex Ameen ) tomberek | 12:40:09 |
| 1 Mar 2023 |
|  Fabián Heredia changed their display name from fabianhjr to Fabián Heredia. | 06:05:16 |
 tgamblin | Can anyone recommend a good contact for python support in Nix? Asking to attempt to involved some folks from Nix in larger Python packaging discussions. | 23:15:03 |
 Alyssa Ross | #python:nixos.org? | 23:37:04 |
| 2 Mar 2023 |
 Robert Hensing (roberth) | February 30 meeting notes; interesting. When was that? | 21:57:18 |
| infinisil | Robert Hensing (roberth): Oh damn, messed up the date, will fix! | 23:19:51 |
| 4 Mar 2023 |
|  nicolabrisotto joined the room. | 17:02:37 |
| 6 Mar 2023 |
| infinisil | @room: The next meeting will take place in ~10 minutes - meeting link - live stream - meeting notes | 15:21:04 |
| infinisil | Pairing with growpotkin ( Alex Ameen ) in https://meet.jit.si/nixpkgs-architecture on using modules for package, notepad: https://pad.lassul.us/lr4EhSckTJSByDLBLcm_-w?edit | 16:41:52 |
| infinisil | * (Edit: Not anymore) Pairing with growpotkin ( Alex Ameen ) in https://meet.jit.si/nixpkgs-architecture on using modules for package, notepad: https://pad.lassul.us/lr4EhSckTJSByDLBLcm_-w?edit | 18:30:17 |
 DavHau | One point that we might want to add to the problems:
Inconsistent configuration styles between NixOS (the module system) and Nixpkgs (function arguments, and an ad hoc config attribute set). | 18:50:28 |
| infinisil | DavHau: Feel free to! | 18:56:44 |
| DavHau | Already in bed. Will do tomorrow | 18:57:51 |
| infinisil | Oh right, good night! | 18:58:08 |
| infinisil | Who's interested in working together on the Rust tooling (involving rnix) for RFC 140? I'd like to schedule a weekly 2 hour call to hack on it together. If you're interested, please fill in your availability here: https://www.when2meet.com/?19082882-QESfj | 19:54:54 |
| infinisil | Wanja Hentze: ^ | 19:55:06 |
| 7 Mar 2023 |
| DavHau | I extended, re-structured and re-ordered the Problems section of the document. Hope that's fine, please check again. | 06:17:52 |
| DavHau | Studying a few guix packages could be worthwhile for this group to see how they handle different language integrations. They already seem to use aspects of modules for their packages. | 06:43:39 |
| DavHau | Though looking at Guix: Defining Package Variants, it seems like their overrides are expressed as transformations, similar like in nixpkgs, and therefore might be as fragile as in nixpkgs due to ordering and merge issues etc. | 06:48:58 |
|  @ozyman:matrix.org joined the room. | 07:58:03 |
|  lassulus joined the room. | 08:19:34 |
 Growpotkin | I felt like overrideAttrs remained useful with modules ( since it allows you to reference prev ), while override was less useful for regular stdenv.mkDerivation ( since these are essentially just freeformType fields ).
overrideAttrs in modules is different from regular overlays because of the merge operation. I personally chose to force a single definition, but you could use lib.pipe or something to compose them ( seems like added complexity without much benefit though IMO ).
Having said all of that, I think having explicit option definitions for most fields will significantly reduce the use of overrides since you'd more likely opt for lib.mkOverride, lib.mkForce, lib.mkDefault, etc for defined options.
| 14:32:47 |
 FRidh |
Where does python.withPackages fit? Kind of creates a new package set
It's a composition using buildEnv behind the scenes.
| 17:57:15 |
| FRidh | I see a couple of use cases identified. I suggest showing how the interface could be for those cases. I am particularly interested in seeing how this is done when you do a composition on packages in a subset and there is an override in that subset :) | 17:58:20 |
