Skip to content

Possibly broken dependency detection #8

@joepie91

Description

@joepie91

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."*

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions