btw, if you use workflows that demand closed-world build-plans (and don't achieve that via file+index:// repos), a useful feature not mentioned by the article you might find useful is
cabal.readthedocs.io/en/late…
Great article by Luke Lau showing off some of #Haskell #cabal 3.2's useful features for everyday work!
lukelau.me/haskell/posts/mak…
Are you aware of downloads.haskell.org/debian… ? It doesn't get easier and more idiomatic than that on Debian IMO.
Fwiw, even though this is yet another thing hlint's defaults keep hatin' my source for, I'm quite happy using U+0027 as prefix-separator in my record fields and constructor names, as in e.g.
hackage.haskell.org/package/…
this trades some verbosity for less cognitive overhead ftw! :-)
...ok, but why insist on forcing a provably incompatible version instead of using version 0.6.0.1 of hackage-security that contains fixups to be *actually* compatible with GHC 8.10's TH API? ;-)
hackage.haskell.org/package/…
This has been debunked many times so just to remind: The problem is that even small chances of failures add-up and propagate through the dep-graph harming/annoying everyone & the longer a semantically unsound buildplan is allowed to circulate, the more costly it becomes to repair
All but the "cabal-install-head" package are supposed to be stable releases (or stable release candidates); if you've run into problems please file a report over at github.com/haskell/cabal/iss… and tell us `cabal --version` as well as the output of `dpkg -l 'cabal-install-*'` !
Sure, make sure /opt/ghc/bin is in your path, then you can use a `-w ghc-7.8.4` CLI flag on the fly to quickly switch between ghc versions or put
packages: .
with-compiler: ghc-7.8.4
into your per-project `cabal.project` configuration file;
see also qfpl.io/posts/multiple-ghcs/
...but are you *really* sure that you built the GHCHQ src+bindist tarballs from that very commit hash and not the one that had been sitting on the ghc/8.8 branch tip until a couple minutes ago, and that now we either need to move the Git tag or scrap the GHCHQ tarball dists?
I've got about a dozen binary builds for Debian & Ubuntu lined up but something's looking inconsistent; can you state which Git commit hash the GHC 8.8.3 release is supposed to be derived from?
IMO @_osa1 makes a good case that the overall cost&issues of adding seemingly neat syntax variations to the language extends far beyond an innocent looking 10-line patch (whose OP might not even be involved w #haskell anymore) and isn't taken srsly enough
osa1.net/posts/2020-01-22-no…
HVR retweeted
We've put together an Awesome list of resources for the #Haskell Cabal build tool 💫 Discover incredible tools and helpful guides all in one place!
And help us to make it even more awesome💅 Share your amazing work if it's anyhow related to Cabal!
kowainik.github.io/projects/…
HVR retweeted
Pleased to say that three and a half months later, we have officially switched to using `cabal-install` instead of `stack` at @HasuraHQ! 🎉 github.com/hasura/graphql-en…
HVR retweeted
🆕 Blog post time!
I wrote about a nice feature for your #Haskell package configurations — "Common Stanzas". Step by step integration showcase and alternative examples (featuring #Dhall) are included.
vrom911.github.io/blog/commo…
Well... I *did* such a PR long ago already... but for some reason it wasn't merged back then... :-(
github.com/actions/cache/pul…