exa/devtools
Benjamin Sago 93bd052c70 Make Vagrant provisioning quieter and faster
• Install fewer Rust components
• Silence the output of some commands
• Only locale-gen the locales we need, and only do it once

While the 'vagrant up' and 'vagrant provision' times are still very long, and these benchmarks are very variable, there's a noticeable improvement here:

• 'vagrant up' has gone from ~244s to ~223s
• 'vagrant provision' has gone from ~21s to ~7s
2020-10-18 01:19:43 +01:00
..
dev-bash.sh Just straight-up roll our own logger 2020-10-10 02:01:12 +01:00
dev-create-test-filesystem.sh More date-related xtests 2020-10-17 21:26:24 +01:00
dev-fixtures.sh More date-related xtests 2020-10-17 21:26:24 +01: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-set-up-environment.sh Make Vagrant provisioning quieter and faster 2020-10-18 01:19:43 +01: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.