!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

419 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
23 Aug 2025
@emilazy:matrix.orgemilybut then corollary: the CI is already not testing what actually gets deployed19:06:55
@raitobezarius:matrix.orgraitobezariusYeah I am not super happy with that 21:43:54
@raitobezarius:matrix.orgraitobezariusWe should lockfile maintain release branches as well21:44:05
@raitobezarius:matrix.orgraitobezariusI recently obtained the technology for it21:44:10
@raitobezarius:matrix.orgraitobezariusThere needs to be wiring up for Gerrit and then happiness may ensue21:44:42
@lunaphied:lunaphied.meLunaphied You want to automate lockfile updates on release branches? I don't see how that fits with tags 22:06:15
@raitobezarius:matrix.orgraitobezariusIdeally, if the nixos-module work land, people will use lixFromNixpkgs or lix from nixpkgs, therefore, tags or not tags, people will stop have a point-in-time set of unmaintained dependencies22:53:48
@raitobezarius:matrix.orgraitobezariusNonetheless, the lix repo CI should use up-to-date dependencies for testing things as it's the closest to what actual users are running (or should be running)22:54:10
@raitobezarius:matrix.orgraitobezariusTherefore, even if this doesn't lead to a release, release branches should have lockfile maintenance22:54:20
@raitobezarius:matrix.orgraitobezarius Because any backport work will benefit from a CI that tests uptodate nixpkgs 22:54:38
@emilazy:matrix.orgemilythe NixOS module calls the package with its own Nixpkgs input anyway23:13:16
@emilazy:matrix.orgemilyin the flake23:13:28
@emilazy:matrix.orgemilyso most users will be using their actual Nixpkgs if they set the follow23:13:30
@emilazy:matrix.orgemilyin any case any new changes to a Lix release branch will never hit EOL Nixpkgs versions and I'm assuming that using Lix from the repo with EOL Nixpkgs versions is also not supported, so testing EOL versions in CI makes little sense for any branch23:14:16
@emilazy:matrix.orgemily aloisw: btw, one of the problems with keeping the old toml11 is that we need the new one for the CMake 4 bump 23:14:46
@emilazy:matrix.orgemilyso I would strongly prefer to just fix this23:14:57
@emilazy:matrix.orgemily(by need I mean: the old one will cause problems with CMake 4)23:15:41
@raitobezarius:matrix.orgraitobezarius
In reply to @emilazy:matrix.org
so most users will be using their actual Nixpkgs if they set the follow
i'm a non flake user :D
23:18:14
@emilazy:matrix.orgemilyactually it is not even about the flake input, I was wrong23:18:51
@emilazy:matrix.orgemilyit sets an overlay23:18:53
@raitobezarius:matrix.orgraitobezariusyeah23:18:57
@emilazy:matrix.orgemilyso it will be using the NixOS system's package set, regardless23:18:59
@raitobezarius:matrix.orgraitobezariushm yep23:19:10
24 Aug 2025
@lunaphied:lunaphied.meLunaphied Uhhhh 00:28:08
@lunaphied:lunaphied.meLunaphiedhm something about that seems off00:28:13
@lunaphied:lunaphied.meLunaphied
In reply to @raitobezarius:matrix.org
i'm a non flake user :D
I really need to get around to that change with supporting overrides in flake-compat
00:28:36
@raitobezarius:matrix.orgraitobezarius just give me https://git.afnix.fr/sprinkles/sprinkles 00:29:20
@lunaphied:lunaphied.meLunaphiedo.o what's this exactly?00:34:46
@raitobezarius:matrix.orgraitobezarius Charles attempts to bring a flake structure to the non-flake world 00:35:05
@raitobezarius:matrix.orgraitobezariusi personally like it, it's growing on me certainly00:35:16

Show newer messages


Back to Room ListRoom Version: 10