Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow customizing the path of the global .tool-versions file #1553

Open
pgilad opened this issue Apr 30, 2023 · 2 comments
Open

Allow customizing the path of the global .tool-versions file #1553

pgilad opened this issue Apr 30, 2023 · 2 comments

Comments

@pgilad
Copy link

pgilad commented Apr 30, 2023

Is your feature request related to a problem? Please describe

The current solution always clutters the user homedir with the .tool-versions (or name override) file

Describe the proposed solution

I would like to have the ability to explicitly set the global .tool-versions alongside with it's path (would usually resort to ~/.config/asdf/.tool-versions myself).
Alternatively - one can just state the base directory for the global .tool-versions file, and then it will allow the ability to use the base path alongside the ASDF_DEFAULT_TOOL_VERSIONS_FILENAME override variable.

Describe similar asdf features and why they are not sufficient

None relevant

Describe other workarounds you've considered

None relevant

@hyperupcall
Copy link
Contributor

hyperupcall commented Apr 30, 2023

If the problem is that .tool-versions automatically clutters the home directory, would you also consider #1351 a fix? Instead of having to set a variable, you can just put the file in one of the asdf base desktop spec directories.

@pgilad
Copy link
Author

pgilad commented Apr 30, 2023

#1351 doesn't handle the global .tool-versions. You need to modify https://github.com/asdf-vm/asdf/blob/master/lib/functions/versions.bash#LL23C18-L23C27 for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants