Newest at the top
| 2025-05-01 22:32:21 +0200 | <sim590> | Soo I build with `v2-build`. |
| 2025-05-01 22:32:08 +0200 | <sim590> | And if I just change the name to `cabal.project.local`, then it works.. |
| 2025-05-01 22:31:54 +0200 | <tomsmeding> | wat |
| 2025-05-01 22:31:52 +0200 | <sim590> | Yeah |
| 2025-05-01 22:31:46 +0200 | <tomsmeding> | and `cabal build` gives `There is no <pkgname>.cabal package file or cabal.project file.`? |
| 2025-05-01 22:31:22 +0200 | <tomsmeding> | oh |
| 2025-05-01 22:31:18 +0200 | <sim590> | `ls .` yields `cabal.project CHANGELOG.md dht.data dht.data_port.txt dhtrunner-commit.msg dist-newstyle docker LICENSE opendht-hs.cabal README.md src todo.txt`. |
| 2025-05-01 22:31:01 +0200 | <tomsmeding> | cabal.project, not project.cabal |
| 2025-05-01 22:30:27 +0200 | <sim590> | While `I'm not though.. The `opendht-hs.cabal` and the `project.cabal` files are both in the current directory. |
| 2025-05-01 22:30:17 +0200 | <tomsmeding> | the `.` is a path to a directory, relative to the cabal.project file, where cabal expects to find a .cabal file |
| 2025-05-01 22:30:16 +0200 | dhil | (~dhil@openvpn-125-1069.inf.ed.ac.uk) (Ping timeout: 276 seconds) |
| 2025-05-01 22:29:50 +0200 | <tomsmeding> | that sounds like you're running cabal in the wrong directory? |
| 2025-05-01 22:29:47 +0200 | nitrix | (~nitrix@user/meow/nitrix) nitrix |
| 2025-05-01 22:29:32 +0200 | <sim590> | Alright, I fixed that, but I still get `There is no <pkgname>.cabal package file or cabal.project file.`. |
| 2025-05-01 22:29:30 +0200 | <mauke> | I mean, it's obvious what you meant |
| 2025-05-01 22:29:25 +0200 | <mauke> | they just just edit-distance the thing |
| 2025-05-01 22:29:06 +0200 | <tomsmeding> | sometimes the tools are right |
| 2025-05-01 22:28:56 +0200 | <sim590> | oops |
| 2025-05-01 22:28:53 +0200 | <int-e> | lol |
| 2025-05-01 22:28:51 +0200 | <sim590> | lol |
| 2025-05-01 22:28:45 +0200 | <tomsmeding> | pacakges != packages |
| 2025-05-01 22:28:44 +0200 | <mauke> | pacak |
| 2025-05-01 22:28:42 +0200 | nitrix | (~nitrix@user/meow/nitrix) (Quit: ZNC 1.9.1 - https://znc.in) |
| 2025-05-01 22:28:38 +0200 | <sim590> | `'pacakges' on line 1` |
| 2025-05-01 22:28:33 +0200 | <sim590> | So it also says: `Warning: /home/simon/prog/opendht-hs/cabal.project: Unrecognized section` |
| 2025-05-01 22:28:17 +0200 | <sim590> | I have that though . |
| 2025-05-01 22:28:01 +0200 | <tomsmeding> | in your case, it's just `packages: .` |
| 2025-05-01 22:27:56 +0200 | <tomsmeding> | sim590: yes, that's because if you have a cabal.project, then cabal expects you to have a `packages:` clause in that file |
| 2025-05-01 22:27:36 +0200 | <sim590> | The weird thing is that if I use `cabal.project` instead of `cabal.project.local`, I get this `Warning: There are no packages or optional-packages in the project`. |
| 2025-05-01 22:27:25 +0200 | tomsmeding | never uses `cabal configure` |
| 2025-05-01 22:27:19 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
| 2025-05-01 22:27:10 +0200 | <tomsmeding> | (and more broadly, cabal.project is configuration for building this project from the source repository, whereas users who depend on your package via hackage will only see the .cabal file) |
| 2025-05-01 22:27:02 +0200 | <int-e> | Unless I'm mixing something up? |
| 2025-05-01 22:26:20 +0200 | <int-e> | AFAIA `cabal configure` puts paths there |
| 2025-05-01 22:26:15 +0200 | <tomsmeding> | sim590: cabal.project.local is intended to be the configuration on your local machine that you don't commit to version control; cabal.project is the one that you _do_ commit |
| 2025-05-01 22:26:06 +0200 | <int-e> | oh and you don't want to commit it to repos because it contains local paths |
| 2025-05-01 22:25:57 +0200 | <sim590> | When? |
| 2025-05-01 22:25:43 +0200 | <int-e> | sim590: the main downside I see is that the config will be overwritten all the time |
| 2025-05-01 22:25:43 +0200 | <tomsmeding> | "enhance diagnostics to clarify type errors ... involving bool" sounds completely unrelated |
| 2025-05-01 22:25:40 +0200 | <sim590> | It's just something I did for another project and it worked, so I assumed I needed that. |
| 2025-05-01 22:25:23 +0200 | <sim590> | I'm not too sure about the consequences of using `.local`? |
| 2025-05-01 22:24:46 +0200 | <tomsmeding> | _what_ |
| 2025-05-01 22:24:01 +0200 | <int-e> | Well regardless of why, the support in .cabal files is not there. |
| 2025-05-01 22:23:53 +0200 | <sim590> | So, the exact issue I'm working with is over here: https://github.com/haskell/c2hs/issues/300#issuecomment-2845352330 |
| 2025-05-01 22:23:09 +0200 | <tomsmeding> | I'm not sure why it can't go in the .cabal file, since it sounds like everyone will need this option. :) |
| 2025-05-01 22:22:55 +0200 | <tomsmeding> | it was |
| 2025-05-01 22:22:43 +0200 | <sim590> | OK. I'll remember that! I thought it was sensible to go straight into the .cabal file, but I guess that's not how it's made. |
| 2025-05-01 22:22:41 +0200 | <tomsmeding> | surely other people will need it too! |
| 2025-05-01 22:22:36 +0200 | <int-e> | if this works anywhere locally it'll be in cabal.project and/or cabal.project.local (and if it works in the latter but not in the former that becomes messy because the file tends to be regenerated by `cabal configure` and the like) |
| 2025-05-01 22:22:34 +0200 | <tomsmeding> | so I'm not sure putting it in cabal.project.LOCAL is really the best choice |