Closed ccoulombe closed 9 months ago
Thanks for your contributions @ccoulombe!
Currently, things are installed in such a way that we look for this file relative to the installation of other scripts.
We recognize this is non-ideal, and have it on our radar to put long-to-linked-pe
in btllib
, but I can't give a timeline for when that will happen unfortunately.
Using the script/binary/file from a virtual environment bin folder which is in the $PATH
, or simply asking where to find the executable using which
ease the puzzle of using relative installation paths.
Thanks @ccoulombe! As discussed, I prefer to retain the current long-to-linked-pe
path behaviour, but use the long-to-linked-pe
found on the PATH, if applicable - See #128.
I have not changed the tests for now, as that is for our own continuous integration - the provided test demo bash script is what to use if you would like to test your installation.
Use
long-to-linked-pe
from$PATH
instead. Never never hardcode a path.