2025/06/05

Newest at the top

2025-06-05 23:24:02 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-06-05 23:23:29 +0200trickard_(~trickard@cpe-51-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-06-05 23:21:45 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-05 23:21:21 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-05 23:18:40 +0200loreto(~loreto@user/loreto) loreto
2025-06-05 23:18:31 +0200loreto(~loreto@user/loreto) (Remote host closed the connection)
2025-06-05 23:16:51 +0200trickard_(~trickard@cpe-51-98-47-163.wireline.com.au)
2025-06-05 23:16:38 +0200trickard_(~trickard@cpe-51-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-06-05 23:16:13 +0200michalz(~michalz@185.246.207.221) (Remote host closed the connection)
2025-06-05 23:15:53 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-05 23:15:46 +0200fp1(~Thunderbi@87-92-23-162.bb.dnainternet.fi) fp
2025-06-05 23:15:29 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-05 23:15:24 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-06-05 23:13:49 +0200ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-06-05 23:10:23 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-06-05 23:09:11 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-05 23:08:51 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-05 23:07:23 +0200 <haskellbridge> <sm> and I assumed shake is being used as a "make" replacement, not a "cabal build" replacement here
2025-06-05 23:06:04 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 244 seconds)
2025-06-05 23:04:47 +0200 <haskellbridge> <sm> I think (?) the packages needed are for the shakefile itself, not for a haskell app being built
2025-06-05 23:03:49 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-05 23:03:25 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-05 23:02:49 +0200 <haskellbridge> <sm> that comment raises interesting new ambiguities
2025-06-05 23:01:12 +0200jespada(~jespada@r179-25-40-226.dialup.adsl.anteldata.net.uy) jespada
2025-06-05 23:00:19 +0200 <sclv> ah -- i see. its "we want to build with shake instead of cabal, but we want a package environment that has all the packages we need to build." you totally _can_ do that with cabal, by installing the packages into a package environment.
2025-06-05 22:59:33 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-06-05 22:59:18 +0200 <haskellbridge> <sm> __monty__ if you are attached to running the shakefile via "shake", that can't ensure dependencies, you'll have to do that yourself as a separate step. That's the reason people make it a cabal/stack script.
2025-06-05 22:58:11 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-05 22:57:49 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Read error: Connection reset by peer)
2025-06-05 22:57:31 +0200 <haskellbridge> <sm> welcome to the thread sclv :)
2025-06-05 22:57:25 +0200jespada(~jespada@r179-25-40-226.dialup.adsl.anteldata.net.uy) (Quit: My Mac has gone to sleep. ZZZzzz…)
2025-06-05 22:56:57 +0200 <sclv> i'm so confused.
2025-06-05 22:56:15 +0200 <__monty__> I'd prefer the specification to be complete regardless of whether someone else wants to use Nix.
2025-06-05 22:56:14 +0200prdak(~Thunderbi@user/prdak) prdak
2025-06-05 22:56:11 +0200 <EvanR> who is in charge of building
2025-06-05 22:56:00 +0200 <EvanR> I'm confused about how shake + cabal can exist in the same project, they're both build tools
2025-06-05 22:55:34 +0200 <sclv> then to have it in place, using nix, just add it to your nix environment. that's what nix is for
2025-06-05 22:55:15 +0200 <haskellbridge> <sm> fair enough
2025-06-05 22:54:59 +0200 <__monty__> I know it's not. It's just how I like to run it, parallels the make + Makefile workflow nicely.
2025-06-05 22:54:44 +0200 <sclv> if you do want an executable in place during some other portion of a cabal build, adding that executable in build-tool-depends _should_ work. however as sm says, i don't believe the shake executable is necessary to run a shakefile.
2025-06-05 22:54:34 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-06-05 22:54:19 +0200 <haskellbridge> <sm> or it runs the shakefile with runhaskell
2025-06-05 22:53:55 +0200 <haskellbridge> <sm> "shake" certainly isn't required to run a shakefile. Here's the main, it seems to try to run ninja: https://github.com/ndmitchell/shake/blob/master/src/Run.hs
2025-06-05 22:53:20 +0200 <__monty__> It's required to run the Shakefile, that's all. I'm just hoping there's a nice way to specify it in a Cabal file to be made available. Is a hypothetical script component with "run-depends: base, aeson, shake" really so outrageous?
2025-06-05 22:51:19 +0200 <haskellbridge> <sm> good question, it seems underdocumented
2025-06-05 22:51:07 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-05 22:50:43 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Read error: Connection reset by peer)
2025-06-05 22:48:57 +0200Unicorn_Princess(~Unicorn_P@user/Unicorn-Princess/x-3540542) (Remote host closed the connection)
2025-06-05 22:48:51 +0200 <geekosaur> okay, that's more or less what I expected, so where does this "shake" executable come in?
2025-06-05 22:48:43 +0200trickard_(~trickard@cpe-51-98-47-163.wireline.com.au)