| 11 Apr 2026 |
 hexa | but that means I need to pick programs from the lixPackageSets manually, correct? | 10:29:46 |
 Primrose (== Léana) | Also, why do we need to overlay the packages depending on nix one by one ? here in advanced change | 10:29:46 |
 K900 | Yeah | 10:29:58 |
| K900 | Because Lix is not a drop-in replacement for cppnix | 10:30:09 |
| Primrose (== Léana) | Would it be possible to just do (final: prev: { nix = prev.lix; }) | 10:30:10 |
| K900 | In terms of C++ API | 10:30:13 |
| K900 | So anything that does not expect Lix will explode | 10:30:22 |
| Primrose (== Léana) | I see | 10:30:23 |
| Primrose (== Léana) | Good to know, thanks a lot! | 10:30:38 |
 zoë (she/her) | was the nixForLinking change not go through in the end? or is it just that the current packages haven't been corrected to use it? | 10:32:52 |
| K900 | nixForLinking did go through, but those packages in the example use the C++ API | 10:33:20 |
| K900 | So a global overlay won't help | 10:33:29 |
| K900 | Unless you also override nixForLinking, which will explode | 10:33:40 |
| zoë (she/her) | * did the nixForLinking change not go through in the end? or is it just that the current packages haven't been corrected to use it? | 10:33:49 |
| zoë (she/her) | ooh, nix-eval-jobs, colmena & co use the c++ api? didn't know that | 10:36:32 |
 Sergei Zimmerman (xokdvium) | Generally anything that depends on the c++ api should now be going through nixComponents for specific versions. | 10:50:25 |
| Sergei Zimmerman (xokdvium) | And pkgs.nix is the cli | 10:50:55 |
| 16 May 2024 |
|  zrsk joined the room. | 13:54:49 |
 samrose | In reply to @lunaphied:lunaphied.me
I think there were a few CLs on the Gerrit but nothing being actively worked The other thing that I could do if it helps is test things and try to find bugs. I did do some C++ work in the past, but may lack the time to do it justice here at least for about 30 days or so | 15:55:29 |
 Qyriad | we are not in any rush 🙂 | 17:20:53 |
| samrose | Would it help to also test out the existing Lix code and try to find issues/bugs etc? | 17:23:21 |
| Qyriad | absolutely | 17:23:41 |
| samrose |
- how do people feel about the existing test suite that comes along with nix source code or Lix?
| 17:23:48 |
| Qyriad | it's pitiful | 17:24:10 |
| samrose | heh | 17:24:16 |
 raitobezarius | expanding it is cool | 17:24:23 |
| raitobezarius | writing new tests for builtins which are not tested | 17:24:30 |
| raitobezarius | new test behaviors, etc. | 17:24:32 |
| Qyriad | we have three flavors of test:
gtest (offer only available in libexpr and libutil) bash script virtual machine
the vast, vast majority of testing is in the "bash script" flavor and it is a mess | 17:25:01 |
| samrose | I was just going to ask on the "functional" tests: do we still like using bash there? | 17:25:56 |
