!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

Load older messages


SenderMessageTime
11 Apr 2026
@k900:0upti.meK900Generally the NixOS module is unnecessary now10:28:24
@k900:0upti.meK900We should probably have a deprecation warning somewhere10:28:31
@k900:0upti.meK900But all the required stuff is in nixpkgs now10:28:41
@leana8959:faefox.devPrimrose (== Léana)I see, thanks !10:29:11
@hexa:lossy.networkhexabut that means I need to pick programs from the lixPackageSets manually, correct?10:29:46
@leana8959:faefox.devPrimrose (== 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:0upti.meK900 Yeah 10:29:58
@k900:0upti.meK900 Because Lix is not a drop-in replacement for cppnix 10:30:09
@leana8959:faefox.devPrimrose (== Léana) Would it be possible to just do (final: prev: { nix = prev.lix; }) 10:30:10
@k900:0upti.meK900In terms of C++ API10:30:13
@k900:0upti.meK900So anything that does not expect Lix will explode10:30:22
@leana8959:faefox.devPrimrose (== Léana)I see10:30:23
@leana8959:faefox.devPrimrose (== Léana)Good to know, thanks a lot!10:30:38
@blokyk:matrix.orgzoë (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:0upti.meK900nixForLinking did go through, but those packages in the example use the C++ API10:33:20
@k900:0upti.meK900So a global overlay won't help10:33:29
@k900:0upti.meK900Unless you also override nixForLinking, which will explode10:33:40
@blokyk:matrix.orgzoë (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
@blokyk:matrix.orgzoë (she/her) ooh, nix-eval-jobs, colmena & co use the c++ api? didn't know that 10:36:32
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Generally anything that depends on the c++ api should now be going through nixComponents for specific versions.10:50:25
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)And pkgs.nix is the cli10:50:55
12 Apr 2026
@crystallord:matrix.orgCrystal changed their profile picture.02:15:01
@leona:leona.isleona changed their profile picture.12:15:57
13 Apr 2026
@Ericson2314:matrix.orgJohn Ericsonhttps://www.numerique.gouv.fr/sinformer/espace-presse/souverainete-numerique-reduction-dependances-extra-europeennes/ good luck!01:52:58
@delroth:delroth.netdelrothwas this meant for the off topic channel?10:01:11
@blokyk:matrix.orgzoë (she/her)i've been thinking for a while: after release 2.99, will lix go to 2.100, or will it roll over to 3.0? given the mess and uproar caused by DetNix 3.0, i think a 2.100 would be a much better idea, but is there anywhere this is explicitly written down?10:46:38
@raitobezarius:matrix.orgraitobezariuswe don't know yet10:49:57
@raitobezarius:matrix.orgraitobezariusif lix decides to do a very large breaking change, it might make sense to go to 3.0, now that 3.0 is already used, maybe we will go to 4.0 directly, idk10:50:17
@raitobezarius:matrix.orgraitobezariusmany options exist10:50:20
@k900:0upti.meK900Honestly just go calver at that point10:59:50

Show newer messages


Back to Room ListRoom Version: 10