scasa icon indicating copy to clipboard operation
scasa copied to clipboard

Symlink to binary not supported but no error provided

Open MehtaKnight01 opened this issue 2 years ago • 0 comments

Running scasa from a symlink is not possible as Scasa expects to be able to access the scasa directory via the "which scasa" command (see SCASA_WRAP_V1.0.0.pl line 36), however, no error message is provided. It is my understanding that using "readlink -f" on the output of the "which scasa" command will return the appropriate directory even if the which scasa command returns the location of the symlink. See https://unix.stackexchange.com/questions/22128/how-to-get-full-path-of-original-file-of-a-soft-symbolic-link

This error is not obvious to the user; Scasa simply "finishes" running without generating an index or count matrix.

MehtaKnight01 avatar Jun 20 '22 18:06 MehtaKnight01