You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The installation instructions say that after installation one can invoke capirca as ~/.local/bin/capirca. However, the installer doesn't install anything in ~/.local/bin. This applies both when installing from a clone of the current git master branch and when installing from PyPI via pip. In both cases, the installation finishes without error, but ~/.local/bin/capirca does not exist:
$ python setup.py install --user
running install
running bdist_egg
running egg_info
creating capirca.egg-info
writing capirca.egg-info/PKG-INFO
writing dependency_links to capirca.egg-info/dependency_links.txt
writing entry points to capirca.egg-info/entry_points.txt
<snip>
Using /home/jhaiduce/.local/lib/python3.10/site-packages
Finished processing dependencies for capirca==2.0.4
$ capirca
bash: capirca: command not found...
$ ls ~/.local/bin/capirca
ls: cannot access '/home/jhaiduce/.local/bin/capirca': No such file or directory
But the capirca package is successfully installed in ~/.local/lib/python3.10/site-packages:
Ah, I see in setup.py there is an entry point aclgen, which does exist in ~/.local/bin. So apparently the readme needs to be updated to reference the aclgen script instead of caprica?
jhaiduce
changed the title
Installer doesn't put anything in ~/.local/bin
Installer doesn't put capirca command in ~/.local/bin
May 3, 2022
The installation instructions say that after installation one can invoke capirca as
~/.local/bin/capirca
. However, the installer doesn't install anything in ~/.local/bin. This applies both when installing from a clone of the current git master branch and when installing from PyPI via pip. In both cases, the installation finishes without error, but ~/.local/bin/capirca does not exist:But the capirca package is successfully installed in ~/.local/lib/python3.10/site-packages:
The text was updated successfully, but these errors were encountered: