The chromedriver executable not being in the search path causes browser automation SW, such as python's webdriver module that uses selenium, to not find the driver out of the box.
I suggest to either put the chromedriver executable under /usr/bin/chromedriver as Debian does, or to symlink the executable to /usr/bin/chromedriver.
I'll create a pull request that creates the symlink. Please let me know if you rather have the executable moved.
The
chromedriver
executable not being in the search path causes browser automation SW, such as python's webdriver module that uses selenium, to not find the driver out of the box.I suggest to either put the
chromedriver
executable under/usr/bin/chromedriver
as Debian does, or to symlink the executable to/usr/bin/chromedriver
.I'll create a pull request that creates the symlink. Please let me know if you rather have the executable moved.