3 ms·
You could also use a package manager utility to list which files are needed, assuming the target binary was installed that way. (pkgs.org lists the files every
by gary_0 5y ago
You could also use a package manager utility to list which files are needed, assuming the target binary was installed that way. (pkgs.org lists the files every package installs, or locally you could run something like `apt-files`).
- cmeacham98 5y agoMaybe check out the --detect flag from the README that claims to do just that?
- gary_0 5y agoOh, wow! They've thought of everything.
- throwaway984393 5y agoThat will detect files in a system package, but not files in a system package depended on by a system package depended on by a system package. It depends on how the distro packages deps and how apps use them. There are apps which use non-linked files that are only provided in extra packages. And even if you walk the whole dependency graph for a single package and export all listed files, you miss files that are created and updated during the setup steps of a package install (which are not listed in the package).
- Brian_K_White 5y agoAs long as the automatic way finds most things, and there is any way to manually include arbitrary things, that is actually perfectly great to me. I don't understand what the complaint or expectation is here.
- throwaway984393 5y agoJust trying to put out there to expect undefined behavior or failures. Users might not understand how applications work and so might expect more than is possible. The strace trick is a nice workaround but I didn't see it in the readme