exa/devtools
Benjamin Sago e95eb5e9fc Vagrant changes
• Get rid of the 'fresh' VM. It just got in the way, taking up more memory when 'vagrant up' was used, and only solved one problem  that was happening three years ago when I was at RustFest and in a programm-y mood.
• Use a more up-to-date Ubuntu image and give the machine more cores.
• Start moving some of the developer tools out of this repo. As I get more and more Rust projects, I don't want the scripts to package them to be repeated in each repository.
2020-10-10 00:21:20 +01:00
..
dev-bash.sh Move the welcoming text to their own files too 2017-10-01 09:49:45 +02:00
dev-help.sh Change user in Vagrantfile 2018-09-26 21:25:50 +01:00
dev-package-for-linux.sh build: use binary name only 2020-07-24 09:03:57 +05: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 Copy weekly changes into macos script 2017-10-08 20:54:18 +01:00
README.md Vagrant changes 2020-10-10 00:21:20 +01:00

exa development tools

These scripts deal with things like packaging release-worthy versions of exa.

They are not general-purpose scripts that youre able to run from your main computer! Theyre intended to be run from the Vagrant machine.