Installer script uses relative paths in compiled program

[2meito]

This causes many issues such as littering .env folders in any directory the script is run.

[Kiramei]

@2meito Thanks for your comment. Can you provide some further information, such as the log?

[pur1fying]

I think some updates for installer is necessary:

1. It’s better to add a config file for installer.py , users can define install parameters arrcording to their computer enviroment. For example : install python or specify an existing python environment.
2. Command in installer.py like

 subprocess.run([env_python_exec, '-m', 'pip', 'install', '-r', './requirements.txt', '-i',
         'https://pypi.tuna.tsinghua.edu.cn/simple', '--no-warn-script-location'], check=True)

Mirror site should not be fixed cause it seems some user can't install requriements when the mirror is https://pypi.tuna.tsinghua.edu.cn/simple

[2meito]

Sorry for not following up earlier.

If you run the following commands:

cd /home/username/Downloads
sudo dpkg -i  BlueArchiveAutoScript_linux_amd64_v1_1_3.deb
sudo BlueArchiveAutoScript

The script will clone the repository to the /home/username/Downloads and any time you want to run BlueArchiveScript, you will have to cd to the directory, otherwise it will create an new installation in the current directory.

Instead of relative paths, (e.g. ./env/bin/python3), we should use full paths (e.g. \home\username\repositories\blue_archive_auto_script\env\bin\python3).

[Kiramei]

Sorry for not following up earlier.

If you run the following commands:

cd /home/username/Downloads

sudo dpkg -i  BlueArchiveAutoScript_linux_amd64_v1_1_3.deb

sudo BlueArchiveAutoScript

The script will clone the repository to the /home/username/Downloads and any time you want to run BlueArchiveScript, you will have to cd to the directory, otherwise it will create an new installation in the current directory.

Instead of relative paths, (e.g. ./env/bin/python3), we should use full paths (e.g. \home\username\repositories\blue_archive_auto_script\env\bin\python3).

Ah... I see it. I'll try to fix the problem in next few weeks.