tree 485b6f9b660c8ff451908bb510cb346bb2477313
parent 25a28c3d472b602bba69326f3f2733d47674813e
author Adam Sadovsky <asadovsky@gmail.com> 1454626679 -0800
committer Adam Sadovsky <sadovsky@google.com> 1454633650 +0000

website: stop failing if 'jiri' exists in PATH

Updates step-by-step.md and setup.md accordingly:
- In step-by-step.md, make sure the 'jiri' tool inside the
  new $JIRI_ROOT takes precedence over any existing 'jiri'
- In setup.md, use the 'jiri' from $JIRI_ROOT instead of
  relying on $PATH

This should fix the test-tutorials-external tests - they
were failing because 'jiri' existed in PATH on Jenkins.

With the changes to step-by-step.md and setup.md, the 'jiri'
check in bootstrap.sh seems unnecessary:

- we already check for $JIRI_ROOT not existing
- we tell contributors to add $JIRI_ROOT/devtools/bin to
  their $PATH
- it should be OK for people to have other copies of 'jiri'
  on their system / in their $PATH, as long as they use the
  right one when working with Vanadium

(An alternative to this CL would be to change the test setup
to temporarily drop 'jiri' from PATH in the test harness,
but that's annoying in its own way...)

Change-Id: Id54cd35e8b1a9b2bfde0212c4f65a391da140f02