Cabal version check fails about ansible-tidalcycles

[cleary]

Hi, it sounds like you're working off a lot of non-standard packaging items which this tool isn't designed to support (with this, start clean and get a vanilla tidal/sc install with repo provided packages).

However, what I'd recommend is editing the vscode playbook, and commenting/removing the tidal role so it will only do the vscode install for you, bypassing all the tidal/sc/Haskell install tasks

[bat-tsagan]

Seems pretty standard to me, installed all the Haskell components from the Haskell repos and GHCUP indicates I'm at the recommended versions. Also, where the Ansible script fails running "cabal --numeric-version", running the same thing directly at a bash prompt produces the desired result. I think I may try the manual route of installing Tidal as I can re-install my system from scratch quite easily (I deliberately decided to install Tidal first because from past experience it's a ***** to get working).

PS. To clarify that last remark,I mean working without ending up with a monumental amount of cruft in your system that affects performance.

PPS. Sorry, forgot to add that I'll try your suggestion first but probably just remove the Haskell tasks since afaic those are up-to-date.

Thanks for responding. Is it better for me/you if I post this kind of thing to the Tidal forum?

[cleary]

Sorry, by "standard" I'm referring to out-of-the-box repos (Ubuntu standard repos).
Yes I could support the Haskell repos, or one of a bunch of ppas - but, in order to provide breadth of support across distro I'm not taking that route.

Yes it's a pain to install, which is why I built this tool - start with a blank system, and just run a playbook. There is no need to install any other packages beforehand (besides git and ansible).

I haven't explicitly tested elementary os either, so depending on where they've diverged from Ubuntu may also be the issue. Dunno, but I can only test/support so many distros 😅