hashimoto-kei opened PR #11329 from hashimoto-kei:hashimoto-kei-patch-1 to bytecodealliance:main:
I don't think an issue is needed for this. Just a brief notice that a new terminal needs to be opened after
wastimeinstallation.Why
wasmtimecannot be executed unless user profile is reloaded.$ curl https://wasmtime.dev/install.sh -sSf | bash $ wastime -V zsh: command not found: wasmtime
hashimoto-kei requested cfallin for a review on PR #11329.
hashimoto-kei requested wasmtime-default-reviewers for a review on PR #11329.
hashimoto-kei edited PR #11329:
I don't think an issue is needed for this. Just a brief notice that a new terminal needs to be opened after
wastimeinstallation.Why
wasmtimecannot be executed unless user profile is reloaded.$ curl https://wasmtime.dev/install.sh -sSf | bash $ wasmtime -V zsh: command not found: wasmtime
pchickey submitted PR review:
I don't think this is good advice - its only required to open a new terminal (or
exec $SHELLor any other number of more shell-specific ways to reload the profile) if the install script needed to create the install dir (defaults to ~/.wasmtime) and add it to path. I think a better approach to this problem would be for the installupdate_profilesub to print instructions when adding to the profile that the user needs toexec $SHELLfor wasmtime to be in their path. (The install script cannot do this on the users behalf.)
bjorn3 commented on PR #11329:
The rustup installer suggest
source ~/.bashrcand similar for other shells.
bjorn3 edited a comment on PR #11329:
The rustup installer suggest running
source ~/.bashrcand similar for other shells.
hashimoto-kei closed without merge PR #11329.
hashimoto-kei updated PR #11329.
hashimoto-kei reopened PR #11329.
hashimoto-kei updated PR #11329.
Last updated: Dec 06 2025 at 06:05 UTC