You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the v2- commands are full of regressions, If you install via v2-install, generally that means that later upgrades don't work.. So I'd stick with v1- for as long as we can.
It is not clear to me what full of regressions refers to here. Is it a correct interpretation that you refer to cabal not handling global libraries well? But it worked somewhat better in v1 than in v2 commands? If so, is our best hope to escape Haskell issues by improving the Tidal binary support? Do you think we could describe our needs / the problem we are facing and open an issue in Cabal?
The text was updated successfully, but these errors were encountered:
Yes basically I meant cabal v2- is broken for people like us who want to install and use libraries, rather than build binaries. I've had some discussions on the cabal issue tracker and the answer there has been that we are not using cabal in the way they expect. The answer to this is the development of a 'cabal env' tool but despite a working prototype this seems to have stalled.
Agreed a binary distribution of tidal would be a great way out of this.
In #9 (comment), @yaxu writes
It is not clear to me what full of regressions refers to here. Is it a correct interpretation that you refer to cabal not handling global libraries well? But it worked somewhat better in v1 than in v2 commands? If so, is our best hope to escape Haskell issues by improving the Tidal binary support? Do you think we could describe our needs / the problem we are facing and open an issue in Cabal?
The text was updated successfully, but these errors were encountered: