Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1 vs v2 commands #10

Open
Zalastax opened this issue Nov 1, 2022 · 1 comment
Open

v1 vs v2 commands #10

Zalastax opened this issue Nov 1, 2022 · 1 comment

Comments

@Zalastax
Copy link
Contributor

Zalastax commented Nov 1, 2022

In #9 (comment), @yaxu writes

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?

@yaxu
Copy link
Member

yaxu commented Nov 3, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants