Closed jmromer closed 2 years ago
This isn't a bug. Setting ASDF_DEFAULT_TOOL_VERSIONS_FILENAME
is meant to be filename change, not full file path change as you show in your example.
Global .tool-versions
is not special from local except it is always $HOME/.tool-versions
. Setting ASDF_DEFAULT_TOOL_VERSIONS_FILENAME
just changes this to: $HOME/$ASDF_DEFAULT_TOOL_VERSIONS_FILENAME
.
From the docs:
ASDF_DEFAULT_TOOL_VERSIONS_FILENAME - The filename of the file storing the tool names and versions. Defaults to .tool-versions. Can be any valid filename. Typically you should not override the default value unless you know you want asdf to ignore .tool-versions files.
asfd global<name> <version>
will always try to write to $HOME/$ASDF_DEFAULT_TOOL_VERSIONS_FILENAME
.
The reason for this is that versions are resolved by walking up the directory tree from the current, and $HOME
is likely in that PATH.
ASDF_DEFAULT_TOOL_VERSIONS_FILENAME
Describe the Bug
Given a customized path for the global
tool-versions
file, When attempting to change the global version used for a given plugin Then ASDF fails to find thetool-versions
fileSteps to Reproduce
$ASDF_DEFAULT_TOOL_VERSIONS_FILENAME
(e.g. /Users/home/.dotfiles/config/asdf/tool-versions)asdf global <plugin> <version>
Expected Behaviour
The global version of the plugin updated to the requested version
Actual Behaviour
Failure message
Environment