!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

423 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.140 Servers

Load older messages


SenderMessageTime
31 Mar 2026
@lisanna-dettwyler:matrix.orgLisanna I'll put together some more information on use cases once it's finalized and join the zulip to discuss the idea 20:32:57
4 Apr 2026
@lotte:chir.rsLotte (it/its)/Cinny (she/her) θΔ& changed their profile picture.10:58:32
@antifuchs:asf.computerantifuchs lix in nixpkgs deprecation-warning about nixpkgs's export of lib.or is pretty funny though. 14:55:46
@antifuchs:asf.computerantifuchssome other deprecation warnings have been very helpful in finding very screwed-up regexes (or things that aren't actual regexes), so overall a fantastic release, thanks everyone who worked on getting these improvements out!15:05:31
@piegames:flausch.socialpiegames lib.or should have died over a decade ago. lib.or is the reason why the precedence is fucked around or as an operator 16:55:38
@antifuchs:asf.computerantifuchsAnything that speeds its demise is very welcome. What a weirdo identifier.17:10:10
@antifuchs:asf.computerantifuchsAlso, it is objectively hilarious17:10:32
5 Apr 2026
@lotte:chir.rsLotte (it/its)/Cinny (she/her) θΔ& changed their profile picture.16:57:20
6 Apr 2026
@lotte:chir.rsLotte (it/its)/Cinny (she/her) θΔ& changed their profile picture.13:47:41
@lotte:chir.rsLotte (it/its)/Cinny (she/her) θΔ& changed their profile picture.13:48:49
7 Apr 2026
@vigress9:matrix.org@vigress9:matrix.org removed their display name V. 🏳️‍⚧️.17:46:19
@vigress9:matrix.org@vigress9:matrix.org left the room.17:47:05
16 May 2024
@aciceri:nixos.devzrsk joined the room.13:54:49
@samrose:matrix.orgsamrose
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:katesiria.orgQyriadwe are not in any rush 🙂17:20:53
@samrose:matrix.orgsamroseWould it help to also test out the existing Lix code and try to find issues/bugs etc?17:23:21
@qyriad:katesiria.orgQyriadabsolutely17:23:41
@samrose:matrix.orgsamrose
  • how do people feel about the existing test suite that comes along with nix source code or Lix?
17:23:48
@qyriad:katesiria.orgQyriadit's pitiful17:24:10
@samrose:matrix.orgsamroseheh 17:24:16
@raitobezarius:matrix.orgraitobezariusexpanding it is cool17:24:23
@raitobezarius:matrix.orgraitobezariuswriting new tests for builtins which are not tested17:24:30
@raitobezarius:matrix.orgraitobezariusnew test behaviors, etc.17:24:32
@qyriad:katesiria.orgQyriad we have three flavors of test:
  1. gtest (offer only available in libexpr and libutil)

  2. bash script

  3. virtual machine


the vast, vast majority of testing is in the "bash script" flavor and it is a mess
17:25:01
@samrose:matrix.orgsamroseI was just going to ask on the "functional" tests: do we still like using bash there?17:25:56
@samrose:matrix.orgsamrosethe last time that I worked on a major nix related cli project that used bash, or bats for testing, over time it became rather kind of hard to maintain17:26:42
@samrose:matrix.orgsamroseI am not usually a big python fan, but in that project we heard from some in the Rust community that they actually use Python to test CLI and seem to have success there. 17:27:59
@qyriad:katesiria.orgQyriadno gods please kill bash testing. the problem is that it's kind of really difficult to migrate an entire test suite and be sure that you actually migrated the test suite correctly and won't lose coverage accidentally in the process, which makes any kind of migration a bit nerve wracking17:28:36
@samrose:matrix.orgsamroseyes it's a rather large undertaking17:28:52
@samrose:matrix.orgsamrosecould be done in chunks17:28:59

Show newer messages


Back to Room ListRoom Version: 10