We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As noted in #41, the shell/powershell installers unconditionally install into cargo home, but we should let the user configure that.
This should possibly support some amount of templating, as seen in the config for cargo-binstall.
Theoretical usecases with strawman syntax:
install-path = "{cargo}"
install-path = "{npm}"
install-path = "~/.my-app/"
install-path = "{xdg}/my-app/"
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
As noted in #41, the shell/powershell installers unconditionally install into cargo home, but we should let the user configure that.
This should possibly support some amount of templating, as seen in the config for cargo-binstall.
Theoretical usecases with strawman syntax:
install-path = "{cargo}"
(use cargo's global install dir)install-path = "{npm}"
(use npm's global install dir?)install-path = "~/.my-app/"
(install to a hardcoded dir in the user's home)install-path = "{xdg}/my-app/"
(install to whatever the hell xdg says you're supposed to do)The text was updated successfully, but these errors were encountered: