Re: [Haskell-cafe] cabal 3.8 pre-released!
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 <mikolaj@well-typed.com> wrote:
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
On 03/06/2022 19.14, Carter Schonwald wrote:
This looks great!
Is the solver being factored out as its own package a new architecture change ?
For any people who like VCS speklunking it started around 1d101e65fba107c1759bfe53df0f0833635a2c5f I'm sure there was much pondering and hawwing and hemming before that but... that commit is my only claim to fame in Cabal history. I gave up trying to make things happen in Cabal a year or so later. There was *soooo* much analysis paralysis that I just couldn't... :( Happy to see the project being more active these days :). At least that's what it looks like from the outside. Cheers,
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 <mikolaj@well-typed.com> wrote:
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)
-
Bardur Arantsson -
Carter Schonwald -
Mikolaj Konarski