Newest at the top
| 2025-05-15 16:52:20 +0200 | SlackCoder | (~SlackCode@66.249.153.49) SlackCoder |
| 2025-05-15 16:51:06 +0200 | euleritian | (~euleritia@dynamic-176-006-131-191.176.6.pool.telefonica.de) |
| 2025-05-15 16:50:39 +0200 | euleritian | (~euleritia@ip2504f9f8.dynamic.kabel-deutschland.de) (Ping timeout: 252 seconds) |
| 2025-05-15 16:48:38 +0200 | Shsl-Junko-POSER | (~Shsl-Junk@50.235.208.178) |
| 2025-05-15 16:48:08 +0200 | Shsl-Junko-POSER | (~Shsl-Junk@50.235.208.178) (Client Quit) |
| 2025-05-15 16:46:59 +0200 | Shsl-Junko-POSER | (~Shsl-Junk@50.235.208.178) |
| 2025-05-15 16:46:41 +0200 | Shsl-Junko-POSER | (~Shsl-Junk@50.235.208.178) (Write error: Broken pipe) |
| 2025-05-15 16:46:26 +0200 | Shsl-Junko-POSER | (~Shsl-Junk@50.235.208.178) |
| 2025-05-15 16:39:04 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-05-15 16:38:41 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-05-15 16:34:37 +0200 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) Tuplanolla |
| 2025-05-15 16:33:36 +0200 | <hellwolf> | yes. use cabal.project, it will work for your case. |
| 2025-05-15 16:33:36 +0200 | <Square> | okok |
| 2025-05-15 16:33:00 +0200 | <merijn> | Since cabal.project's intended purpose is "orchestrating/configuring build configurations of (potentially) unpublished code" |
| 2025-05-15 16:32:59 +0200 | <Square> | I wanted to test out a new project layout wo moving so many files, that was the reason I resorted to the "../" approach |
| 2025-05-15 16:32:35 +0200 | <hellwolf> | but that was a stupid idea. don't. |
| 2025-05-15 16:32:26 +0200 | <hellwolf> | I remember I hacked it once with ln -s ../src . |
| 2025-05-15 16:32:06 +0200 | <merijn> | Square: The intended purpose for cabal files is to describe packages (i.e. self-contained code that can go on to hackage, etc.) which means roots outside of that folder make no sense. You (probably) want a combination of cabal.project and multiple cabal files |
| 2025-05-15 16:31:11 +0200 | <Square> | thanks |
| 2025-05-15 16:31:10 +0200 | <Square> | merijn, gotcha |
| 2025-05-15 16:31:06 +0200 | Xe | (~Xe@perl/impostor/xe) Xe |
| 2025-05-15 16:30:49 +0200 | <merijn> | Square: relative paths outside of the root of the cabal file are not allowed an will never be, that's a feature, not a bug |
| 2025-05-15 16:28:19 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net) (Ping timeout: 245 seconds) |
| 2025-05-15 16:26:41 +0200 | Xe | (~Xe@perl/impostor/xe) (Quit: ZNC 1.9.1 - https://znc.in) |
| 2025-05-15 16:23:41 +0200 | <hellwolf> | you should use cabal.project to specify a new local project, and let your other local project depend on it. |
| 2025-05-15 16:23:16 +0200 | <hellwolf> | cabal error message should be very clear of that, as far as I remember. |
| 2025-05-15 16:23:04 +0200 | <hellwolf> | "relative path from parent folder" as I suspected. |
| 2025-05-15 16:08:28 +0200 | <c_wraith> | It sounds like whatever you're trying to do should be solved by cabal.project instead |
| 2025-05-15 16:07:16 +0200 | <Square> | hs-source-dirs |
| 2025-05-15 16:07:02 +0200 | <Square> | Ok.. to be specific. I cannot have a hs-source-dir that starts with "../some/path" |
| 2025-05-15 16:05:31 +0200 | rvalue | (~rvalue@user/rvalue) rvalue |
| 2025-05-15 16:05:00 +0200 | rvalue | (~rvalue@user/rvalue) (Read error: Connection reset by peer) |
| 2025-05-15 16:04:43 +0200 | <c_wraith> | I'm pretty sure that's what has everyone confused by the question. Of course it works with relative paths, that's the only thing anyone ever uses. |
| 2025-05-15 16:04:00 +0200 | <c_wraith> | I have never seen a non-relative path in that field |
| 2025-05-15 16:00:55 +0200 | <Square> | hellwolf, exactly. But yeah, could be a nix + haskell issue. |
| 2025-05-15 15:57:11 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net) |
| 2025-05-15 15:49:16 +0200 | <hellwolf> | otherwise, it doesn't make sense, since it's the basic feature. |
| 2025-05-15 15:48:52 +0200 | <hellwolf> | do you mean cannot be relative path from parent folders |
| 2025-05-15 15:48:39 +0200 | <hellwolf> | huh? |
| 2025-05-15 15:48:13 +0200 | ubert | (~Thunderbi@p200300ecdf1b8afc99002e8c4e21755f.dip0.t-ipconnect.de) (Quit: ubert) |
| 2025-05-15 15:46:46 +0200 | FragByte | (~christian@user/fragbyte) FragByte |
| 2025-05-15 15:44:49 +0200 | FragByte | (~christian@user/fragbyte) (Quit: Quit) |
| 2025-05-15 15:41:27 +0200 | son0p | (~ff@2800:e6:4000:5cf7:2aa0:f8ac:1dbc:787d) son0p |
| 2025-05-15 15:37:35 +0200 | <Square> | I thought they fixed it in cabal 3 |
| 2025-05-15 15:37:21 +0200 | <Square> | It could be a haskell + nix problem. But I remember it was a known bug in cabal 2.x |
| 2025-05-15 15:36:51 +0200 | <merijn> | They are/should be, no? |
| 2025-05-15 15:36:40 +0200 | <merijn> | Square: How so? |
| 2025-05-15 15:35:40 +0200 | <Square> | hs-source-dirs in cabal cannot be relative it seems? |
| 2025-05-15 15:31:01 +0200 | fp | (~Thunderbi@2001:708:20:1406::1370) (Ping timeout: 248 seconds) |
| 2025-05-15 15:24:23 +0200 | ttybitnik | (~ttybitnik@user/wolper) ttybitnik |