Hello there @chriskuehl !

Thank you for this simple yet useful piece of software. I often use python instead of shell script for quick tools, even when I'm not working on Python projects. Hence I always have a venv around and I leverage the fact that its built around a normal UNIX filesystem to install tools into it (awscli, gcloud, terraform, installed under venv/opt/<thing> for instance).

I wanted to do the same thing with rust and wrote a rust env management script that will optionally embed the rust env within an existing virtualenv.

Instead of pushing my tool to pypi, I could simply contribute it here. Would you be interested?

Here is the command line interface

rustenv somepath # unstall rust under somepath/rust, exactly as it is today

python -m venv somepath
rustenv somepath  # install rust under somepath/opt/rust

python -m venv somepath
source somepath/bin/activate
rustenv # install rust under somepath/opt/rust

python -m venv somepath
source somepath/bin/activate
rustenv someotherpath # install rust under someotherpath/rust

When embedding the rustenv within a Python virtualenv, the activate script is updated.

I (and a couple people I work with) am really interested in this feature. I also see that you did not feel the need to make any changes in the last couple years, so here are the options I'd like your opinion about.

• Accept this feature as a contribution
• Not interested in rustenv anymore? transfer it to me so I can add the feature and maintain it
• Not interested/not responding at all? No problem, I'll simply distribute it under another name.

Have a nice day!

currently it produces output like this:

$ rustenv renv
info: downloading installer
info: profile set to 'default'
info: default host triple is x86_64-unknown-linux-gnu
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2022-08-11, rust version 1.63.0 (4b91a6ea7 2022-08-08)
info: downloading component 'cargo'
info: downloading component 'clippy'
info: downloading component 'rust-docs'
info: downloading component 'rust-std'
info: downloading component 'rustc'
info: downloading component 'rustfmt'
info: installing component 'cargo'
info: installing component 'clippy'
info: installing component 'rust-docs'
 18.3 MiB /  18.3 MiB (100 %)   9.5 MiB/s in  1s ETA:  0s
info: installing component 'rust-std'
 26.1 MiB /  26.1 MiB (100 %)  14.4 MiB/s in  1s ETA:  0s
info: installing component 'rustc'
 54.3 MiB /  54.3 MiB (100 %)  15.9 MiB/s in  3s ETA:  0s
info: installing component 'rustfmt'
info: default toolchain set to 'stable-x86_64-unknown-linux-gnu'

  stable-x86_64-unknown-linux-gnu installed - rustc 1.63.0 (4b91a6ea7 2022-08-08)


Rust is installed now. Great!

To get started you need Cargo's bin directory (/tmp/explains/renv/rust/bin) in 
your PATH
environment variable. This has not been done automatically.

To configure your current shell, run:
source "/tmp/explains/renv/rust/env"

the last little bit there is especially problematic since it's not how rustenv is intended to work

The script called rustenv-proxy use readlink -f but in Mac OS uses BSD like commands and this option is not supported. It seems that the easiest fix is to remove rustenv-proxy and create links for each rust binary. Is there any reason to use rustenv-proxy?

This happens e.g. in bash scripts (as opposed to logged-in sessions).

$ cat test.sh
#!/bin/bash
set -euo pipefail
. renv/bin/activate

$ ./test.sh  
renv/bin/activate: line 6: PS1: unbound variable

It should probably skip setting the PS1 in this case entirely?

It would be nice to be able to check the version:

´´´

bin/rustenv --version
usage: rustenv [-h] destination
rustenv: error: the following arguments are required: destination

´´´´

Currently this seems working for Linux only. It would be good if it works in Windows also ?

Any plans for this ?