Thomas> What's the usual directory layout if an executable needs
Thomas> additional private files (library.zip, something.so and so on)?
As with all things Unix there several different ways to skin the cat. One
common installation scheme is Python's. The interpreter lives in
/usr/local/bin/pythonM.m and all the version-specific stuff lives in places
like /usr/local/lib/pythonM.m and /usr/local/include/pythonM.m where M and m
are the major and minor versions. Another way is to create an
application-specific directory in a prefix directory like /usr/local, then
create bin, etc, lib and include directories underneath. Apache and
Berkeley DB prefer this setup. Either way, there is a known relationship
between the executable and the files it relies on.
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4