exa/devtools
Benjamin Sago 895808e945 Show friendlier warnings when binaries don’t exist
Also, allow the --release flags to be passed to the build-exa and test-exa commands.
2017-10-02 10:22:50 +02:00
..
dev-bash.sh Move the welcoming text to their own files too 2017-10-01 09:49:45 +02:00
dev-download-and-check-release.sh Add a release-checking script 2017-10-01 12:28:23 +02:00
dev-help-testvm.sh Give the testing VM commands and help text 2017-10-01 12:37:35 +02:00
dev-help.sh Move the welcoming text to their own files too 2017-10-01 09:49:45 +02:00
dev-package-for-linux.sh Linux check for Linux script 2017-10-01 10:55:38 +02:00
dev-run-debug.sh Show friendlier warnings when binaries don’t exist 2017-10-02 10:22:50 +02:00
dev-run-release.sh Show friendlier warnings when binaries don’t exist 2017-10-02 10:22:50 +02:00
dev-versions.sh Move the welcoming text to their own files too 2017-10-01 09:49:45 +02:00
local-package-for-macos.sh Add macOS packaging script 2017-10-01 10:55:14 +02:00
README.md Add a dev help 2017-10-01 12:44:29 +02:00

exa development tools

These scripts deal with things like packaging release-worthy versions of exa and making sure the published versions actually work.

They are not general-purpose scripts that youre able to run from your main computer! Theyre intended to be run from the Vagrant machines — they have commands such as package-exa or check-release that execute them instead.