Files or paths are not found towards the end of the installation script
Steps to Reproduce
Execute linux_install.sh in an empty folder
Possible Solution
The script is executing at the wrong path.
Context
Executed on Ubuntu 22.04
Successfully installed lollms-10.0.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
./linux_install.sh: line 107: cd: utilities/pipmaster: No such file or directory
Obtaining file:///home/lotkas/lollms
ERROR: file:///home/lotkas/lollms does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.
./linux_install.sh: line 125: requirements.txt: No such file or directory
ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'
cp: cannot stat 'scripts/linux/linux_run.sh': No such file or directory
cp: cannot stat 'scripts/linux/linux_conda_session.sh': No such file or directory
Creating a bin dir (required for llamacpp binding)
Select the default binding to be installed:
1) None (install the binding later) 6) Remote binding - open_ai
2) Local binding - ollama 7) Remote binding - mistral_ai
3) Local binding - python_llama_cpp 8) Remote binding - gemini
4) Local binding - bs_exllamav2 9) Remote binding - xAI
5) Remote binding - open_router 10) Remote binding - groq
#? 2
python: can't open file '/home/zoos/bindings_zoo/ollama/__init__.py': [Errno 2] No such file or directory
*******************************************************************
*******************************************************************
Expected Behavior
Installation Completed without errors
Current Behavior
Files or paths are not found towards the end of the installation script
Steps to Reproduce
Execute
linux_install.sh
in an empty folderPossible Solution
The script is executing at the wrong path.
Context
Executed on Ubuntu 22.04
Screenshots