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

beamup directories are named after Rust ecosystem properties #52

Open
lpil opened this issue Nov 25, 2024 · 1 comment · May be fixed by #58
Open

beamup directories are named after Rust ecosystem properties #52

lpil opened this issue Nov 25, 2024 · 1 comment · May be fixed by #58

Comments

@lpil
Copy link

lpil commented Nov 25, 2024

# curl --proto '=https' --tlsv1.2 -LsSf https://github.com/tsloughter/beamup/releases/download/v0.6.0/beamup-installer.sh | sh
downloading beamup 0.6.0 aarch64-unknown-linux-gnu
installing to /root/.cargo/bin
  beamup
everything's installed!

To add $HOME/.cargo/bin to your PATH, either restart your shell or run:

    source $HOME/.cargo/env (sh, bash, zsh)
    source $HOME/.cargo/env.fish (fish)

Seeing as this is a BEAM tool I don't think it should have any public references to Rust.

@tsloughter
Copy link
Owner

Hm, I swear I had a reason it ended up that way despite not originally doing so... I'll need to dig through cargo dist docs again to see if what they support has changed. I'd prefer ~/.local/bin (unless overridden by the user) but I think part of it was I didn't want it to create that dir if it didn't exist, tho maybe that isn't really something I should care about.

Let me look into this again and hopefully improve it in some fashion.

@tsloughter tsloughter linked a pull request Nov 29, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants