Dhall-haskell: The windows version of dhall-lsp-server in the latest release is different from mac and linux

[akshaymankar]

[jneira]

Same for dhall-jsonand dhall-bash, it is taking the version of the main dhall package the github main tag instead the specific cabal version one for them.
But the version of the executable inside the zip is the correct one (we can check it with the --version cli option).
We have to revise the appveyor script to correct this.

[Gabriel439]

Thanks for the catch! I just fixed the version numbers on them

[sjakobi]

Shouldn't we still fix the AppVeyor config?

[sjakobi]

Seems like we need something similar to what we have for Travis:

https://github.com/dhall-lang/dhall-haskell/blob/8e52b9da45135fe926dd876461cb3ba6798ab326/.travis-functions.sh#L1-L3

https://github.com/dhall-lang/dhall-haskell/blob/8e52b9da45135fe926dd876461cb3ba6798ab326/.travis.yml#L50-L52

According to https://www.appveyor.com/docs/getting-started-with-appveyor-for-linux/#bash-and-powershell we could even try re-using these functions.

[jneira]

ugh, i feel a strange itch when i see regular expressions 😄

I think a more generic solution would be to ask for the version to executables being released:

mk_release_name() { echo "$1-$($1 --version )-x86_64-macos.tar.bz2"; } 

(or ($1 version), it will great that all executables would have the same way to get it)

[Gabriel439]

If only there were a configuration language that could be used to generate both Cabal files and Bash to keep them both in sync … 🤔

j/k I think using sed is fine. I just couldn't resist the joke 🙂

[sjakobi]

Heads up that this still hasn't been fixed @Gabriel439 – the .zips still need to be manually renamed! :/