14.07.2019, 16:30
Quote:Why not use "$HOME/.hybrid/vapoursynth" for the VS installation?having executables in hidden directories seems wrong
I think it would be better to keep the config/settings separated from the tools.
Quote:I have "$HOME/bin" added to PATH and I try to avoid installing directories in there.When installing as root I would add Vapoursynth under /opt/vapoursynth, as a user $HOME/opt/vapoursynth would probably be the best alternative.
regarding vsViewer:
Adding a vsViewer_withenv.sh and calling that in Hybrid works fine and it's easy, I think hardcoding a PYTHONPATH would be a mistake.
---
Maybe installing Vapoursynth system wide (under /opt/vapoursynth) is the cleanest way to go about the whole thing.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.