-
|
It is a Ubuntu Server 22.04. I installed pip and then ran pip install beets, and then ran beet config -p as the doc said, but beet was not found. The document did not give any more information, so I used "find" and found that it is under "~/.local/bin". That path was not in my path by default. Why does Beets install the binaries there? Shouldn't it be somewhere where it is in path? Or if not, doesn't the doc at least say that it is installed there so that users would execute ".~/.local/bin/beet cofig -p" instead of "beet config -p"? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
This is a feature of pip: You will probably want to extend your |
Beta Was this translation helpful? Give feedback.
-
|
@HubKing I marked the answer. Did that work out for you? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, thanks. |
Beta Was this translation helpful? Give feedback.
This is a feature of pip:
https://unix.stackexchange.com/questions/712177/defaulting-to-user-installation-because-normal-site-packages-is-not-writeable
You will probably want to extend your
$PATH, as alluded to here:https://beets.readthedocs.io/en/stable/faq.html#say-command-not-found