2025/04/25

Newest at the top

2025-04-25 16:25:25 +0200__jmcantrell__(~weechat@user/jmcantrell) jmcantrell
2025-04-25 16:20:30 +0200Googulator(~Googulato@81.183.235.203) (Ping timeout: 240 seconds)
2025-04-25 16:20:19 +0200Teacup(~teacup@user/teacup) Teacup
2025-04-25 16:19:57 +0200Teacup(~teacup@user/teacup) ()
2025-04-25 16:18:29 +0200TheCoffeMaker(~TheCoffeM@user/thecoffemaker) TheCoffeMaker
2025-04-25 16:17:44 +0200Digit(~user@245.144.208.46.dyn.plus.net)
2025-04-25 16:17:28 +0200TheCoffeMaker(~TheCoffeM@user/thecoffemaker) (Ping timeout: 252 seconds)
2025-04-25 16:17:00 +0200Googulator47(~Googulato@81.183.235.203)
2025-04-25 16:14:01 +0200JuanDaugherty(~juan@user/JuanDaugherty) JuanDaugherty
2025-04-25 16:06:19 +0200Digit(~user@245.144.208.46.dyn.plus.net) (Ping timeout: 276 seconds)
2025-04-25 16:03:43 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) ft
2025-04-25 16:01:55 +0200euphores(~SASL_euph@user/euphores) euphores
2025-04-25 15:53:56 +0200euphores(~SASL_euph@user/euphores) (Quit: Leaving.)
2025-04-25 15:51:27 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 276 seconds)
2025-04-25 15:50:27 +0200pavonia(~user@user/siracusa) siracusa
2025-04-25 15:49:55 +0200Square(~Square@user/square) (Ping timeout: 260 seconds)
2025-04-25 15:46:07 +0200euleritian(~euleritia@dynamic-176-006-135-143.176.6.pool.telefonica.de)
2025-04-25 15:45:34 +0200euleritian(~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de) (Ping timeout: 252 seconds)
2025-04-25 15:41:20 +0200euleritian(~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de)
2025-04-25 15:41:03 +0200euleritian(~euleritia@dynamic-176-006-135-143.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-04-25 15:38:16 +0200vpan(~vpan@212.117.1.172) (Quit: Leaving.)
2025-04-25 15:36:53 +0200Digit(~user@245.144.208.46.dyn.plus.net)
2025-04-25 15:35:33 +0200mceresa(~mceresa@user/mceresa) mceresa
2025-04-25 15:32:10 +0200dhil(~dhil@openvpn-125-1069.inf.ed.ac.uk) dhil
2025-04-25 15:28:20 +0200Digit(~user@user/digit) (Ping timeout: 260 seconds)
2025-04-25 15:25:43 +0200euleritian(~euleritia@dynamic-176-006-135-143.176.6.pool.telefonica.de)
2025-04-25 15:25:25 +0200euleritian(~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de) (Ping timeout: 260 seconds)
2025-04-25 15:11:33 +0200Square(~Square@user/square) Square
2025-04-25 15:08:51 +0200Square2(~Square4@user/square) (Ping timeout: 268 seconds)
2025-04-25 15:05:42 +0200TMA(tma@twin.jikos.cz) TMA
2025-04-25 15:04:30 +0200 <ii8> Alright, I'll try that then, thanks
2025-04-25 15:01:57 +0200 <haskellbridge> <ozkutuk> I guess pinning index-state would be enough then
2025-04-25 15:01:45 +0200 <ii8> s/considend/consistent
2025-04-25 15:01:24 +0200tromp(~textual@2001:1c00:3487:1b00:c44:d27d:c88:929f)
2025-04-25 15:01:19 +0200 <ii8> merijn: In that case it would be fine, I'm assuming a consistend build environment
2025-04-25 15:01:01 +0200 <haskellbridge> <ozkutuk> or a package could depend on, say, "unix" package if the OS is linux and "Win32" if its windows
2025-04-25 14:59:55 +0200haritz(~hrtz@user/haritz) haritz
2025-04-25 14:59:55 +0200haritz(~hrtz@2a01:4b00:bc2e:7000::2) (Changing host)
2025-04-25 14:59:55 +0200haritz(~hrtz@2a01:4b00:bc2e:7000::2)
2025-04-25 14:59:53 +0200 <merijn> ii8: Could be a flag that detects whether C library X is on the system and use that if it is
2025-04-25 14:59:25 +0200 <ii8> If the index-state is fixed and I'm building from the same source tarball, can the flags still end up different?
2025-04-25 14:58:52 +0200 <ii8> I'm not sure what that means
2025-04-25 14:58:18 +0200 <merijn> ii8: Because they're auto toggle
2025-04-25 14:57:52 +0200 <ii8> Why might the flags change?
2025-04-25 14:55:10 +0200 <haskellbridge> <ozkutuk> for example, it also records the set package flags for the dependencies
2025-04-25 14:54:56 +0200 <haskellbridge> <ozkutuk> ii8: freeze file provides stronger guarantees wrt determinism compared to index-state
2025-04-25 14:54:56 +0200 <merijn> ii8: The solver is deterministic, so index-state should be sufficient
2025-04-25 14:54:41 +0200 <merijn> ii8: Right, but if you run the build in a dir with a cabal.project file you can force a specific index-state just fine
2025-04-25 14:53:21 +0200 <ii8> jackdk: not an option for me I think
2025-04-25 14:52:36 +0200 <ii8> I guess assuming it contains an index-state setting. Is that enough or is the freeze file needed too to fix the build?