Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#73359 - [pyenv] Incomplete PATH
Attached to Project:
Community Packages
Opened by Giovanni Kraushaar (ExaFusion) - Friday, 14 January 2022, 12:51 GMT
Last edited by David Runge (dvzrv) - Tuesday, 18 January 2022, 08:17 GMT
Opened by Giovanni Kraushaar (ExaFusion) - Friday, 14 January 2022, 12:51 GMT
Last edited by David Runge (dvzrv) - Tuesday, 18 January 2022, 08:17 GMT
|
DetailsDescription:
Consider symlinking all executables in /usr/share/pyenv/libexec to /usr/bin. If not commands like pyenv-install would return errors such as "/usr/bin/pyenv-install: line 142: pyenv-hooks: command not found". This could be solved by the user by exporting "PATH=$PATH:/usr/share/pyenv/libexec", but why bother the user with an undocumented extra step when the result is, unfortunately, in both cases, cluttering the PATH even more? |
This task depends upon
Closed by David Runge (dvzrv)
Tuesday, 18 January 2022, 08:17 GMT
Reason for closing: Not a bug
Additional comments about closing: Please refer to `man 1 pyenv` (https://man.archlinux.org/man/pyenv.1) on how to use pyenv
Tuesday, 18 January 2022, 08:17 GMT
Reason for closing: Not a bug
Additional comments about closing: Please refer to `man 1 pyenv` (https://man.archlinux.org/man/pyenv.1) on how to use pyenv
Why are you not using `pyenv install <target>` though?