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

install-path customization #235

Closed
Tracked by #41
Gankra opened this issue May 3, 2023 · 0 comments · Fixed by #284
Closed
Tracked by #41

install-path customization #235

Gankra opened this issue May 3, 2023 · 0 comments · Fixed by #284
Labels
feature request New feature or request
Milestone

Comments

@Gankra
Copy link
Member

Gankra commented May 3, 2023

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)
@Gankra Gankra added the feature request New feature or request label May 3, 2023
@Gankra Gankra added this to the 0.1.0 milestone May 3, 2023
@Gankra Gankra mentioned this issue Sep 18, 2023
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant