Adding new depenencies to the workflows

[wwmm]

Hi @vchernin. Now that the gsl library package is needed the workflow configuration has to be updated. How to add it?

[wwmm]

Oh... The Arch Linux workflow uses the PKGBUILD in our repository? I did not notice this before. By the way this pkgbuild build fails in my computer. Strange...

[vchernin]

Of course it later fails to build locally when installing the files...

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/mesonbuild/mesonmain.py", line 153, in run
    return options.run_func(options)
  File "/usr/lib/python3.10/site-packages/mesonbuild/minstall.py", line 758, in run
    with open(os.path.join(log_dir, 'install-log.txt'), 'w', encoding='utf-8') as lf:
PermissionError: [Errno 13] Permission denied: 'meson-private/../meson-logs/install-log.txt'

[wwmm]

Hm is EasyEffects stored in /home/wallace/easyeffects?

No. When using the PKGBUILD I usually go to an empty folder and run makepkg -si. So makepkg has to download the sources first. So not having the line source=("easyeffects::git+https://github.com/wwmm/easyeffects.git") is the first problem. But restoring it is not enough.

[wwmm]

Maybe we should have 2 pkgbuild files. One for the workflow and another for general usage.

[vchernin]

So not having the line source=("easyeffects::git+https://github.com/wwmm/easyeffects.git") is the first problem.

I see, for CI both the flatpak and the arch build try to get the local files, as we can't assume the files in master are the ones we want.

Maybe we should have 2 pkgbuild files. One for the workflow and another for general usage.

Yeah I don't see a better way to support both use cases.

[wwmm]

I created a new pkgbuild only for local usage.