-
Notifications
You must be signed in to change notification settings - Fork 234
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
mise install-into node@20 ~/.nodes/20
#1039
Comments
Maybe |
kind of a silly one: |
|
I'd also like this. I'll mention And there could be an environmental variable one could set for that sys. path if it differs from the standard/default sys. path. Or when you call |
Just chiming in to express my interest in this in the context of #512 / #996 still. So far my approach was to make stuff that went to
and probably more. I also tried to customize e.g. the Ruby build by passing Naming wise, as a user I would have expected this to be an option for Alternatively, a new |
Another idea, in addition to |
rtx install-into node@20 ~/.nodes/20
mise install-into node@20 ~/.nodes/20
I want a way to use rtx to install a tool to an arbitrary directory (one not managed by rtx). This way rtx can be a replacement for tools like
node-build
and you can use it to just fetch tools with a consistent syntax.I'm open to ideas on the naming. Some thoughts:
rtx install --to|--into
—not really a fan since it's quite different behavior and syntax (this can only support a single tool and doesn't reference.tool-versions
files)rtx install-direct
rtx install-export
rtx export
The text was updated successfully, but these errors were encountered: