tree 7f519b92f0e82feddaaa04070aa28ca922f99b93
parent 0e5f2d8e11dbb6b88a97a9b253e38019ab1b92b6
author Sam Clegg <sbc@chromium.org> 1595379871 -0700
committer GitHub <noreply@github.com> 1595379871 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfF5CfCRBK7hj4Ov3rIwAAdHIIAFkH+HV1TecybTVPonRlJMk7
 fie64v8zcAQI+Cqz+s+3ahzGnqTxnsdjlJHbhOmHJQI+hN9pd94ftuSMUcyJw08X
 3Nfm7RJAzKGqxWGfYgGUCNK93950qpjvoSDtGnazt8czOVOVaEtJ1VWazBERiHwE
 aQorVdUrx8CLwOeOkMxrJvImR0sawurFFcxSr5R6y1ZkKaE1jSVe2UVeJK3scPw+
 w9r0JOdHnp6w/uNf0+uY+Roen0wTXVRx+uyMezWmgp/TZKwc8ZOBTwCSlcqtKeyf
 oXFEE+mb9dmi0f9BAkLLcV0btwfmMjPGsdIL82HCa5qRYmxnPoT7PhFYrnHBy88=
 =8CF8
 -----END PGP SIGNATURE-----
 

Improve activation message (#562)

* Improve activation message

The activation message is now IMHO more informative and
actionable:

```
$ emsdk activate latest
Setting the following tools as active:
   node-12.18.1-64bit
   releases-upstream-e7e39da9c81faecd9ecf44065cee864d76e4e34d-64bit

Next steps:
- To conveniently access emsdk tools from the command line,
  consider adding the following directories to your PATH:
    $HOME/wasm/emsdk
    $HOME/wasm/emsdk/node/12.18.1_64bit/bin
    $HOME/wasm/emsdk/upstream/emscripten
- This can be done for the current shell by running:
    source "$HOME/wasm/emsdk/emsdk_env.sh"
- Configure emsdk in your bash profile by running:
    echo 'source "$HOME/wasm/emsdk/emsdk_env.sh"' >> $HOME/.bash_profile
```

* .