Newest at the top
| 2025-10-26 23:49:18 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-10-26 23:44:51 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-26 23:44:11 +0100 | <davean> | Sadly, a LOT of it was on twitter, or in private email, and twitter is very hard to cite these days. |
| 2025-10-26 23:43:00 +0100 | <davean> | Not as agressive as https://web.archive.org/web/20191122170832/https://twitter.com/haskdev/status/820932892385808384 mind you |
| 2025-10-26 23:42:48 +0100 | <davean> | snoyman was pretty agresive on it. |
| 2025-10-26 23:41:08 +0100 | Shark8 | (~Shark8@c-174-56-102-109.hsd1.nm.comcast.net) (Ping timeout: 244 seconds) |
| 2025-10-26 23:41:04 +0100 | <davean> | Yah, https://www.snoyman.com/blog/2017/01/stackage-design-choices/ has some oblique references to the policy |
| 2025-10-26 23:38:16 +0100 | Dhark8 | (~Shark8@c-174-56-102-109.hsd1.nm.comcast.net) |
| 2025-10-26 23:35:50 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-10-26 23:34:27 +0100 | <geekosaur> | it broke a lot of people back when that was the recommendation |
| 2025-10-26 23:33:42 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-10-26 23:32:45 +0100 | <sm> | ah I take it back, it's not that important. |
| 2025-10-26 23:32:42 +0100 | <c_wraith> | I lived through it. As a victim. |
| 2025-10-26 23:32:24 +0100 | <sm> | do show us, please :) |
| 2025-10-26 23:32:20 +0100 | <c_wraith> | Which broke a lot of things |
| 2025-10-26 23:32:14 +0100 | <c_wraith> | yes, it did. There was a specific recommendation to not put upper bounds on package dependencies |
| 2025-10-26 23:31:23 +0100 | <sm> | stack never did that |
| 2025-10-26 23:30:28 +0100 | <c_wraith> | Stack has mostly stopped telling its users to make hackage worse for everybody, so I don't dislike it as much as I used to. But it still doesn't fix any problem I actually have. |
| 2025-10-26 23:29:32 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-26 23:27:59 +0100 | <haskellbridge> | <sm> If you wonder why known-compatible snapshots are needed, given that all hackage packages specify compatibility bounds: a package's bounds aren't always correct or accurate; they can change at any time; and cabal's dynamic solving of them can, too. A snapshot provides more reproducibility. It's also a natural place to do extra quality control, or to start other packaging efforts. |
| 2025-10-26 23:27:31 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2025-10-26 23:25:07 +0100 | ttybitnik | (~ttybitnik@user/wolper) ttybitnik |
| 2025-10-26 23:25:00 +0100 | werneta | (~werneta@71.83.160.242) (Quit: Lost terminal) |
| 2025-10-26 23:22:57 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-26 23:22:48 +0100 | ttybitnik | (~ttybitnik@user/wolper) (Remote host closed the connection) |
| 2025-10-26 23:22:46 +0100 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2025-10-26 23:21:18 +0100 | sam113101 | (~sam@modemcable200.189-202-24.mc.videotron.ca) sam113101 |
| 2025-10-26 23:20:54 +0100 | sam113101 | (~sam@modemcable200.189-202-24.mc.videotron.ca) (Remote host closed the connection) |
| 2025-10-26 23:20:22 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-10-26 23:18:26 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 272 seconds) |
| 2025-10-26 23:16:10 +0100 | <haskellbridge> | <sm> a new release on hackage appears automatically in the next stackage nightly (if it is configured there and builds there). A new lts is cut from the current nightly every so often (depends eg on ghc releases). Also lts snapshots get updated. |
| 2025-10-26 23:13:43 +0100 | myxos | (~myxos@65.25.110.175) myxokephale |
| 2025-10-26 23:13:37 +0100 | karenw | (~karenw@user/karenw) karenw |
| 2025-10-26 23:11:54 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds) |
| 2025-10-26 23:11:42 +0100 | <haskellbridge> | <sm> stackage is "stable hackage". If you're familiar with Debian, stackage is to hackage as debian is to github, roughly. It provides a set of snapshots of known-compatible packages from the continually-updated hackage. |
| 2025-10-26 23:11:18 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen |
| 2025-10-26 23:11:08 +0100 | tromp | (~textual@2001:1c00:3487:1b00:b825:23c0:1f89:fdbd) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-10-26 23:10:46 +0100 | myxokephale | (~myxos@65.25.110.175) (Ping timeout: 256 seconds) |
| 2025-10-26 23:08:21 +0100 | <haskellbridge> | <sm> https://stackage.org is the essential page, here you can see what snapshots exist and what package versions are in each |
| 2025-10-26 23:07:31 +0100 | <haskellbridge> | <sm> (hopefully..) |
| 2025-10-26 23:07:26 +0100 | <haskellbridge> | <sm> omentic a quick read of the stack docs would make things a lot clearer ? |
| 2025-10-26 23:07:07 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-26 23:01:58 +0100 | machinedgod | (~machinedg@d75-159-126-101.abhsia.telus.net) machinedgod |
| 2025-10-26 22:59:06 +0100 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 252 seconds) |
| 2025-10-26 22:56:25 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-10-26 22:51:19 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-10-26 22:47:16 +0100 | dmj`_ | (uid72307@id-72307.hampstead.irccloud.com) (Quit: Connection closed for inactivity) |
| 2025-10-26 22:47:16 +0100 | dmj` | (uid72307@id-72307.hampstead.irccloud.com) (Quit: Connection closed for inactivity) |
| 2025-10-26 22:46:13 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 246 seconds) |
| 2025-10-26 22:41:06 +0100 | jreicher | (~user@user/jreicher) jreicher |