Closed alexandre1985 closed 4 years ago
This bug can be reproduced if, for example, you have:
$ PATH=/home/johndoe/scripts:/usr/local/bin:/usr/bin
$ which protonvpn-cli
/home/johndoe/scripts/protonvpn-cli
$ protonvpn-cli --update
There is no bug, protonvpn-cli
is not supposed to be moved. You should have made a ln -s /usr/local/bin/protonvpn-cli /home/johndoe/scripts
instead.
The choice of the installation directory could be given to the user, but that's another PR…
Alright. I understand. I'm gonna close this pull request.
Well, this is just my opinion, I'm not the maintainer here. Maybe you should wait for a review by @kaplun
I cannot Reopen (don't know why). @kaplun please give some feedback
The
--update
flag was not working on my system. I also tried do--install
then--update
onprotonvpn-cli
but still gave the the same error:This happened because
protonvpn-cli
may not be on the hard-coded path of "/usr/local/bin/protonvpn-cli". This assumption (that was on the script) may be wrong.So, this fixes this issue and gives the ability for
protonvpn-cli
script to reside in any directory. In my opinion, this is the correct behaviour forprotonvpn-cli
.