!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

Load older messages


SenderMessageTime
9 Oct 2024
@jade_:matrix.orgjade_there is basically nothing actually conditional on flakes enabled20:59:48
@jade_:matrix.orgjade_there is "the new cli does not let you use it without nix-command enabled". but like. that's not the thing that causes flake maintenance pain at all21:00:13
@kfears:matrix.orgKFears (tragedy arc)Wait, so why have them at all?21:00:14
@jade_:matrix.orgjade_because half of the ecosystem including us depend on them21:00:29
@kfears:matrix.orgKFears (tragedy arc)Like, can't you just like say "use flake-compat" and just not do flakes?21:00:35
@jade_:matrix.orgjade_no, flake-compat is a joke21:00:42
@kfears:matrix.orgKFears (tragedy arc)Figured21:00:48
@jade_:matrix.orgjade_ it's missing a bunch of obscure features that will cause bug reports if they are missing. imo the status quo is fine except insofar as we cannot touch the flakes code safely 21:01:21
@jade_:matrix.orgjade_which does suck, but there is so much else to do21:01:46
@jade_:matrix.orgjade_flakes, in spite of being extremely broken, are merely an entry point into the other 90% of lix that is also very busted and in ways that actually matter to large scale usage and overall maintainability much more21:02:27
@jade_:matrix.orgjade_we can leave flakes in amber and still have plenty of useful things to do21:02:35
@kfears:matrix.orgKFears (tragedy arc)Hopefully some path forward will appear once "everything else" is done21:03:06
@kfears:matrix.orgKFears (tragedy arc)My condolences for having to work on all of this21:03:24
@kfears:matrix.orgKFears (tragedy arc)It sounds like the legacy codebase from hell, straight up21:03:45
@jade_:matrix.orgjade_i also hate that in spite of being an absolute mess, flakes are a moving target in cppnix and continue to gain more features while simultaneously being unmaintainable.21:08:21
@jade_:matrix.orgjade_https://git.lix.systems/lix-project/lix/src/370ac940dd7816ad4052fafa4e0f8d17784fa16b/src/libfetchers/fetchers.cc#L135-L148 type of compat code21:08:45
@kfears:matrix.orgKFears (tragedy arc)
In reply to @jade_:matrix.org
https://git.lix.systems/lix-project/lix/src/370ac940dd7816ad4052fafa4e0f8d17784fa16b/src/libfetchers/fetchers.cc#L135-L148 type of compat code
That doesn't seem too bad
21:21:31
@jade_:matrix.orgjade_no, it is ridiculous actually21:21:43
@jade_:matrix.orgjade_it is that a test is relying on our stderr output21:21:48
@kfears:matrix.orgKFears (tragedy arc)I mean, it's a stupid block of code that shouldn't really be here, but it's a fairly minor block code21:21:57
@jade_:matrix.orgjade_ we cannot change our logs or else we might break a test 21:22:09
@jade_:matrix.orgjade_ that's ridiculous 21:22:14
@kfears:matrix.orgKFears (tragedy arc)
In reply to @jade_:matrix.org
it is that a test is relying on our stderr output
Well, that part is just insanity
21:22:17
@kfears:matrix.orgKFears (tragedy arc)Wait, what does "Nixpkgs fileset lib tests" mean?21:22:47
@k900:0upti.meK900 lib.filesets 22:40:44
@k900:0upti.meK900Which is also broken for another reason now 22:40:51
@k900:0upti.meK900So that's fun 22:40:54
@jade_:matrix.orgjade_wait did we regress it or did nixpkgs regress it?22:51:42
@jade_:matrix.orgjade_if we regressed it, fucking hell :(22:51:46
@k900:0upti.meK900Neither 22:53:29

Show newer messages


Back to Room ListRoom Version: 10