Hello! The first 3.8 series cabal release candidate is available. Install via ghcup config add-release-channel \ https://raw.githubusercontent.com/haskell/ghcup-metadata/master/ghcup-prerel...; ghcup install cabal 3.8.0.20220526 or manually from https://downloads.haskell.org/cabal/cabal-install-3.8.1.0-rc1/. We, the cabal team, are completely dependent on our invaluable contributors and collaborators, thanks to whom this pre-release is possible. Therefore, please test extensively and if anything critical is missing or broken that you'd like to see fixed in 3.8.1.0-final, let us know on the bug tracker. There is still a narrow window to change things and the cabal team will try to guide you along and help you implement them. The dynamic list of known grave bugs that could plausibly be solved for 3.8 is at https://github.com/haskell/cabal/issues?q=is%3Aopen+is%3Aissue+label%3A%22pr... At the time of writing none of the bugs on the list is blocking the final 3.8 release. Changelogs are at https://github.com/haskell/cabal/blob/Cabal-v3.8.1.0-rc1/release-notes/Cabal... https://github.com/haskell/cabal/blob/cabal-install-v3.8.1.0-rc1/release-not... The list of all authors of cabal is the git commit log. You are great. Happy hacking, Mikolaj
On Fri, 3 Jun 2022, Mikolaj Konarski wrote:
Hello! The first 3.8 series cabal release candidate is available. Install via
ghcup config add-release-channel \ https://raw.githubusercontent.com/haskell/ghcup-metadata/master/ghcup-prerel...; ghcup install cabal 3.8.0.20220526
or manually from
https://downloads.haskell.org/cabal/cabal-install-3.8.1.0-rc1/.
What about an upload as package candidate at Hackage?
Hi Henning,
What about an upload as package candidate at Hackage?
Here you go (but note that package candidates are transient so these are going to vanish at some point): https://hackage.haskell.org/package/cabal-install-3.8.0.20220526/candidate https://hackage.haskell.org/package/cabal-install-solver-3.8.0.20220526/cand... https://hackage.haskell.org/package/Cabal-3.8.0.20220526/candidate https://hackage.haskell.org/package/Cabal-syntax-3.8.0.20220526/candidate Let me know if they don't work. Cheers, Mikolaj
This looks great!
Is the solver being factored out as its own package a new architecture
change ?
On Fri, Jun 3, 2022 at 5:27 AM Mikolaj Konarski
Hi Henning,
What about an upload as package candidate at Hackage?
Here you go (but note that package candidates are transient so these are going to vanish at some point):
https://hackage.haskell.org/package/cabal-install-3.8.0.20220526/candidate
https://hackage.haskell.org/package/cabal-install-solver-3.8.0.20220526/cand... https://hackage.haskell.org/package/Cabal-3.8.0.20220526/candidate https://hackage.haskell.org/package/Cabal-syntax-3.8.0.20220526/candidate
Let me know if they don't work.
Cheers, Mikolaj _______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
This looks great!
Thank you. :O)
Is the solver being factored out as its own package a new architecture change ?
It's a new old change, many years in the brewing by generations of cabal developers and now finally (to be) released. We are equally proud of the separation of Cabal-syntax package, again a collaborative effort, started with a mega-commit by Patrick Dougherty. A warning though: the APIs of the new packages are not mature yet, because not enough people use them and give feedback, because they are not mature yet. So expect lots of breakage, guarded by major version bumps. E.g., we re-export too much stuff from Cabal-syntax to limit the breakage of Cabal, to give users a sporting chance to transition to the split API before it's the only one available. All the best, Mikolaj
doing those two pieces is *amazing* and jailbreaks a lot of amazing
tooling/experiments being possible in userspace! props to all who were
involved
On Fri, Jun 3, 2022 at 2:56 PM Mikolaj Konarski
This looks great!
Thank you. :O)
Is the solver being factored out as its own package a new architecture change ?
It's a new old change, many years in the brewing by generations of cabal developers and now finally (to be) released. We are equally proud of the separation of Cabal-syntax package, again a collaborative effort, started with a mega-commit by Patrick Dougherty.
A warning though: the APIs of the new packages are not mature yet, because not enough people use them and give feedback, because they are not mature yet. So expect lots of breakage, guarded by major version bumps. E.g., we re-export too much stuff from Cabal-syntax to limit the breakage of Cabal, to give users a sporting chance to transition to the split API before it's the only one available.
All the best, Mikolaj
participants (3)
-
Carter Schonwald -
Henning Thielemann -
Mikolaj Konarski