tree 627748819ebca60d98fd2e392651dddf0ec8ae4a
parent 2b720e547355182d0b78d59d269bd17561dfac2e
author Sam Clegg <sbc@chromium.org> 1613425614 -0800
committer GitHub <noreply@github.com> 1613425614 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgKuvOCRBK7hj4Ov3rIwAAdHIIAFjYH5JnfRGPF4yvnvScROUU
 GXfuwzndrB1XCcUZN8elbMyFbdGwifnC+qEpH91KEjuND1cn2Gr8UkWBkxu0/cRz
 eG8KiUWU8WN0VGKwLNbBdggGhfUa9E3GfPmLdC6dw8ggy3YG6fKCMRQmJ4VCKB1V
 sIjmjMSbenkb6dUbDhuRccmwq9j+CPO/Oi14iRiY2hwg+NVqqBvXsbO6DBMCeYwf
 4CEOzsZahYFK3/J6p5YiSyw44onw4FhqEAsBctQAfIymXUz0iXxzomQswZdSWmmB
 6JYFTIYFHxNDuJd3YQ6OHjS8jC4q5j4DaL8AuJfKIQVpFOmPma3CvzizwLD4O98=
 =6EG0
 -----END PGP SIGNATURE-----
 

Avoid adding our java or python to the PATH (#706)

For Java we use the value in the config file so it doesn't need to be in
the PATH.

For python, all our tools should launch via scripts that check for
EMSDK_PYTHON so having python in the PATH for emsdk users should not be
needed.

The motivation for this is that we don't want to clobber any existing
python or java versions that users might already have in their PATH.

This is the easy part of #705.