[ new ] install script for the standard library #2895
Conversation
|
|
||
| # Double check that the command exists | ||
| if ! [ -x "$(command -v $AGDA_EXEC)" ]; then | ||
| throwError "'$AGDA_EXEC' is not a valid executable" |
There was a problem hiding this comment.
Should we check if e.g. $HOME/.cabal/bin/$AGDA_EXEC exists and suggest that the user should be adding $HOME/.cabal/bin/ to their PATH?
There was a problem hiding this comment.
You can get cabal's default install path from cabal with cabal path --installdir
|
In theory this looks great. How cross platform is this and what do we need to do to support a new release? It looks like we just update the lookup table? |
|
It won't work on windows but I'm keeping it as simple as possible in the hope it'd work on And, indeed, the only update would be to the lookup table. |
| # Downloading and extracting the standard library | ||
| STDLIB_TARBALL_NAME="/tmp/agda-stdlib-$STDLIB_VERSION.tar.gz" | ||
| STDLIB_TARBALL_URL="https://github.com/agda/agda-stdlib/archive/$STDLIB_TAG.tar.gz" | ||
| wget -O "$STDLIB_TARBALL_NAME" "$STDLIB_TARBALL_URL" -o logs/wget |
There was a problem hiding this comment.
Catch errors and report them?
gallais
force-pushed
the
install-script
branch
from
62a2c03 to
493080f
Compare
Keep asking the user until we get a valid Agda executable
gallais
force-pushed
the
install-script
branch
from
3037ebf to
eba7fa7
Compare
gallais
force-pushed
the
install-script
branch
from
a903fd3 to
7c4e75f
Compare
|
I am quite happy with the current script. I have included a command you can copy/paste in a terminal to test it. |
3 participants
curl-based command for users to runFor testing purposes, using the latest version of the script on my branch: