Newest at the top
| 2025-08-03 12:58:22 +0200 | trickard | (~trickard@cpe-56-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-08-03 12:57:53 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2025-08-03 12:57:25 +0200 | tromp | (~textual@2001:1c00:3487:1b00:1c21:f6c3:9146:cddf) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-08-03 12:56:44 +0200 | fizbin | (~fizbin@2601:84:8601:2604:65a2:2790:1327:34c5) |
| 2025-08-03 12:53:31 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-08-03 12:52:11 +0200 | fizbin | (~fizbin@2601:84:8601:2604:65a2:2790:1327:34c5) (Read error: Connection reset by peer) |
| 2025-08-03 12:50:48 +0200 | caubert | (~caubert@user/caubert) caubert |
| 2025-08-03 12:46:17 +0200 | <haskellbridge> | <sm> I don’t do PVP exactly, but the same general idea. If there’s a user-visible breaking change, that’s a major version bump, etc. |
| 2025-08-03 12:45:10 +0200 | <euouae> | Fair enough, I'll try to follow PVP |
| 2025-08-03 12:44:48 +0200 | <euouae> | I see now, my bad |
| 2025-08-03 12:44:45 +0200 | <euouae> | Oh is that what he said? I thought that he said that the cabal program that built the app should be the same version as the lib |
| 2025-08-03 12:44:20 +0200 | <haskellbridge> | <sm> When I’m releasing a package like that, I consider both the API of the library and the UI/UX of the app. PVP is less formal for an app, but you can pretty much apply the same principle. |
| 2025-08-03 12:42:41 +0200 | <haskellbridge> | <sm> A package that provides both apps and libraries (typically one of each) is pretty common. A release of this package will have a version that applies to both the app and library (like lxsameer said). There’s no sensible way to give them different versions in that scenario I think. |
| 2025-08-03 12:42:03 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2025-08-03 12:41:34 +0200 | gmg | (~user@user/gehmehgeh) (Remote host closed the connection) |
| 2025-08-03 12:41:14 +0200 | <euouae> | If that's a thing? |
| 2025-08-03 12:38:29 +0200 | <haskellbridge> | <sm> euouae, are you wondering how to pick PVP-compliant version numbers for an application ? |
| 2025-08-03 12:37:28 +0200 | caubert | (~caubert@user/caubert) (Ping timeout: 240 seconds) |
| 2025-08-03 12:35:29 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-08-03 12:31:16 +0200 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: zzz) |
| 2025-08-03 12:24:49 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2025-08-03 12:23:13 +0200 | euandreh | (~Thunderbi@189-31-61-8.user3p.v-tal.net.br) (Remote host closed the connection) |
| 2025-08-03 12:22:09 +0200 | <euouae> | Morj, hm... fair |
| 2025-08-03 12:21:45 +0200 | <euouae> | You have a project.cabal file. It has a version: field. That one. |
| 2025-08-03 12:21:32 +0200 | <euouae> | lxsameer: I've specified multiple times |
| 2025-08-03 12:20:07 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-08-03 12:17:46 +0200 | <haskellbridge> | <Morj> I think most of my binaries are at a perpetual 0.1.0.0 |
| 2025-08-03 12:16:44 +0200 | <haskellbridge> | <Morj> Otherwise you can just put whatever |
| 2025-08-03 12:16:41 +0200 | <haskellbridge> | <Morj> Sometimes you can think of a binary as a library with a weird linkage. Especially evident in command-line interfaces where someone at some point will want to use you in a script - then you can use the version to signify breakage as usual for this use-case |
| 2025-08-03 12:16:25 +0200 | <lxsameer> | what version are you talking about then? |
| 2025-08-03 12:16:13 +0200 | <euouae> | I'm talking about the version: field of the .cabal file for a project with a `library` and an `executable`... |
| 2025-08-03 12:15:22 +0200 | <euouae> | the same version of what? |
| 2025-08-03 12:14:29 +0200 | <lxsameer> | if you want to to distribute your app and library together, highly recommend using the same version for both |
| 2025-08-03 12:14:03 +0200 | <lxsameer> | hpack is just a handy tool, you will still use cabal, it just generate the cabal file for you. |
| 2025-08-03 12:13:34 +0200 | <euouae> | cabal works for me, I'm not sure if I need hpack |
| 2025-08-03 12:13:11 +0200 | <euouae> | The x.y.z.w version is explained for a library (major minor patch etc) but it's not clear what it means (if anything) for an app + library |
| 2025-08-03 12:12:47 +0200 | <euouae> | oh no, what I'm asking is, how should I set my own package's version |
| 2025-08-03 12:12:29 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-08-03 12:12:17 +0200 | fizbin | (~fizbin@2601:84:8601:2604:65a2:2790:1327:34c5) |
| 2025-08-03 12:11:45 +0200 | <lxsameer> | and for cabal version you provide a minimum version that you want to support in your cabal file or package file (in case of hpack) |
| 2025-08-03 12:11:12 +0200 | <lxsameer> | use hpack |
| 2025-08-03 12:10:38 +0200 | <euouae> | the libraries are the src/*.hs files |
| 2025-08-03 12:10:31 +0200 | <euouae> | yeah the cabal version |
| 2025-08-03 12:09:25 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2025-08-03 12:08:40 +0200 | <lxsameer> | euouae: what libraries? and what versioning are you referring to? the cabal version? or dependency versions? |
| 2025-08-03 12:07:30 +0200 | <euouae> | Oops (said hi twice) I'm trying to write an app that also comes with some library files. How do I deal with the x.y.z.w versioning of cabal? |
| 2025-08-03 12:06:57 +0200 | <euouae> | Hey all |
| 2025-08-03 12:06:14 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 260 seconds) |
| 2025-08-03 12:06:04 +0200 | <euouae> | Hello |
| 2025-08-03 12:06:01 +0200 | euouae | (~euouae@user/euouae) euouae |