!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

Load older messages


SenderMessageTime
16 May 2024
@qyriad:katesiria.orgQyriad even if you throw a UsageError? 23:54:51
@delroth:delroth.netdelrothwell yeah, look at the code23:55:00
@delroth:delroth.netdelrothit catches (...)23:55:03
@qyriad:katesiria.orgQyriad what 23:55:11
@qyriad:katesiria.orgQyriad fucking hell 23:55:21
@jade_:matrix.orgjade_burn it23:55:27
@jade_:matrix.orgjade_we should fix that catch23:55:35
@qyriad:katesiria.orgQyriad kill catch (...) with fire basically anywhere we can 23:55:49
@delroth:delroth.netdelrothI wonder what's the funniest parsing exception I could trigger which would lead nix to try and parse something as a flake23:56:46
@qyriad:katesiria.orgQyriad I want to fuzz that parser so badly 23:57:04
@jade_:matrix.orgjade_fuzzing is cat behaviour23:57:20
@puck:puck.moepuck 23:57:52
@jade_:matrix.orgjade_ puck: any opinions on choosing to intentionally leave the includes in their current location but still explode pkg-config and linking, vs also moving includes to lix/? 23:58:46
@puck:puck.moepuckmove it. people should use pkg-config always even under nixpkgs23:59:06
@puck:puck.moepuckor, hrm23:59:13
@puck:puck.moepuckno, that'd break anyways23:59:18
@puck:puck.moepucki was thinking of the `foo -> <nix/foo>23:59:24
@puck:puck.moepuck * i was thinking of the foo -> <nix/foo> thing 23:59:25
@jade_:matrix.orgjade_ yes, but lix/ includes do actually affect downstreams if they are including things via #include <nix/nixexpr.hh> 23:59:30
@jade_:matrix.orgjade_but otoh we want to explode our include paths very aggressively in teh future anyhow23:59:51
@jade_:matrix.orgjade_so shrug23:59:53
@puck:puck.moepucksymlinks :D23:59:57
17 May 2024
@jade_:matrix.orgjade_ maybe the c api should be in nix/ still 00:00:02
@puck:puck.moepuckwe can have compat pkg-config entries if we really care00:00:05
@jade_:matrix.orgjade_we should not have compat pkg-config00:00:14
@jade_:matrix.orgjade_because we don't have api compat00:00:18
@jade_:matrix.orgjade_we would just like to not explode peoples actual application code that badly for no reason i guess00:00:31
@puck:puck.moepuck
In reply to @jade_:matrix.org
maybe the c api should be in nix/ still
oh, the C api is in the root of -isystem anyways; but i think we can discuss that; i might do a 1:1 with horrors about this some point soon
00:01:01
@puck:puck.moepuck(i'd like to get the C api in soonish because it'd mean we can run zilch on it)00:01:13
@puck:puck.moepuck (mind you, https://puck.moe/git/zilch/tree/core/nix/default.nix?id=ae0f39a7b7eeef67442f96dd461648369fc47e0f#n3) 00:01:34

There are no newer messages yet.


Back to Room ListRoom Version: 10