You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a look at the dependency detection logic, and if my reading of the code is correct, it could produce false positives.
For example, given a check for the libz entry, it would check for the path $usr_path/lib/libz*, which means that even if no libz.so or similar existed, something like libzanzibar.so (which would be an entirely different library!) would still match, and therefore the script would incorrectly presume that libz is installed.
My Bash is a little rusty so I'm unsure whether this assessment is correct, but if it is, then a fix would probably be to do something like the following instead (note the dot at the end):
so_files="$usr_path/lib/$so."*
The text was updated successfully, but these errors were encountered:
That doesn't seem to work with Postgres and Ruby libs and since there currently aren't any conflicts I'm not worried.
I'll leave this open though as a reminder.
I had a look at the dependency detection logic, and if my reading of the code is correct, it could produce false positives.
For example, given a check for the
libz
entry, it would check for the path$usr_path/lib/libz*
, which means that even if nolibz.so
or similar existed, something likelibzanzibar.so
(which would be an entirely different library!) would still match, and therefore the script would incorrectly presume thatlibz
is installed.My Bash is a little rusty so I'm unsure whether this assessment is correct, but if it is, then a fix would probably be to do something like the following instead (note the dot at the end):
The text was updated successfully, but these errors were encountered: