asdf/bin/private/asdf-exec

#!/usr/bin/env bash

# remove this asdf-exec file when releasing >=0.6.5
echo "asdf is self upgrading shims to new asdf exec ..."

asdf_dir="$(dirname "$(dirname "$(dirname "$0")")")"
# shellcheck source=lib/utils.bash
source "$asdf_dir/lib/utils.bash"
rm "$(asdf_data_dir)"/shims/*
"$asdf_dir"/bin/asdf reshim
shim_name=$(basename "$2")

echo "asdf: now running $shim_name"

exec "$shim_name" "${@:3}"
Fix #1: Better to stick to a single common shell Referred a couple other version managers. The advantage is not having to maintain the scripts for other shells (bash comes by default everywhere I've seen). 2015-05-18 22:14:08 -07:00			`#!/usr/bin/env bash`
Just use a subshell, no other way; Thanks to kurahaupo on #bash IRC for helping out 2015-05-17 03:44:20 -07:00
Test that `asdf exec` works even if asdf shims are not in PATH. 2019-01-19 19:09:53 -07:00			`# remove this asdf-exec file when releasing >=0.6.5`
			`echo "asdf is self upgrading shims to new asdf exec ..."`
get version for package in asdf-exec 2015-05-14 18:06:17 -07:00
New shim metadata to allow many plugins with same executable names Features * New shim version meta-data allows shims to not depend on a particular plugin nor on its relative executable path (#431) Upgrading requires shim re-generation and should happen automatically by `asdf-exec`: `rm -rf ~/.asdf/shims/` followed by `asdf reshim` * Added lots of tests for shim execution. We now make sure that shim execution obeys plugins hooks like `list-bin-paths` and `exec-path`. * Shim exec is now performed by a new `bin/private/asdf-tool-exec` that might be faster for most common use case: (versions on local .tool-versions file) but fallbacks to slower `get_preset_version_for` which takes legacy formats into account. * Shim exec recommends which plugins or versions to set when command is not found. Fixed Bugs * Allow many plugins to provide shims with same executable name (#431) 2019-01-19 03:12:52 -07:00			`asdf_dir="$(dirname "$(dirname "$(dirname "$0")")")"`
Add .bash file extensions to files containing code executed by Bash 2020-03-02 10:44:31 -07:00			`# shellcheck source=lib/utils.bash`
			`source "$asdf_dir/lib/utils.bash"`
New shim metadata to allow many plugins with same executable names Features * New shim version meta-data allows shims to not depend on a particular plugin nor on its relative executable path (#431) Upgrading requires shim re-generation and should happen automatically by `asdf-exec`: `rm -rf ~/.asdf/shims/` followed by `asdf reshim` * Added lots of tests for shim execution. We now make sure that shim execution obeys plugins hooks like `list-bin-paths` and `exec-path`. * Shim exec is now performed by a new `bin/private/asdf-tool-exec` that might be faster for most common use case: (versions on local .tool-versions file) but fallbacks to slower `get_preset_version_for` which takes legacy formats into account. * Shim exec recommends which plugins or versions to set when command is not found. Fixed Bugs * Allow many plugins to provide shims with same executable name (#431) 2019-01-19 03:12:52 -07:00			`rm "$(asdf_data_dir)"/shims/*`
			`"$asdf_dir"/bin/asdf reshim`
			`shim_name=$(basename "$2")`
Move out reshim and exec 2015-05-10 10:25:42 -07:00
New shim metadata to allow many plugins with same executable names Features * New shim version meta-data allows shims to not depend on a particular plugin nor on its relative executable path (#431) Upgrading requires shim re-generation and should happen automatically by `asdf-exec`: `rm -rf ~/.asdf/shims/` followed by `asdf reshim` * Added lots of tests for shim execution. We now make sure that shim execution obeys plugins hooks like `list-bin-paths` and `exec-path`. * Shim exec is now performed by a new `bin/private/asdf-tool-exec` that might be faster for most common use case: (versions on local .tool-versions file) but fallbacks to slower `get_preset_version_for` which takes legacy formats into account. * Shim exec recommends which plugins or versions to set when command is not found. Fixed Bugs * Allow many plugins to provide shims with same executable name (#431) 2019-01-19 03:12:52 -07:00			`echo "asdf: now running $shim_name"`
Use source and set env vars for exec-env 2015-05-21 02:05:26 -07:00
New shim metadata to allow many plugins with same executable names Features * New shim version meta-data allows shims to not depend on a particular plugin nor on its relative executable path (#431) Upgrading requires shim re-generation and should happen automatically by `asdf-exec`: `rm -rf ~/.asdf/shims/` followed by `asdf reshim` * Added lots of tests for shim execution. We now make sure that shim execution obeys plugins hooks like `list-bin-paths` and `exec-path`. * Shim exec is now performed by a new `bin/private/asdf-tool-exec` that might be faster for most common use case: (versions on local .tool-versions file) but fallbacks to slower `get_preset_version_for` which takes legacy formats into account. * Shim exec recommends which plugins or versions to set when command is not found. Fixed Bugs * Allow many plugins to provide shims with same executable name (#431) 2019-01-19 03:12:52 -07:00			`exec "$shim_name" "${@:3}"`