The better approach is to do only dynamic linking with dependency isolation (side-by-side multiple versions/configurations of a library that don't conflict with

The better approach is to do only dynamic linking with dependency isolation (side-by-side multiple versions/configurations of a library that don't conflict with itself. no more RPM upgrade dependency hell.), package managed as idempotent transactions (preferably pre and post snapshotted with something like zfs or btrfs), garbage collected (dependency tracked) library packages like how habitat or nix does it: every unique, no duplicates library installed in its own unique directory. This means no duplicates, no missing dependencies, no breaking dependencies, no duplication of static and dynamic code hacky toolchain kludges. It works with existing systems instead of redoing things, adding more complexity instead of making it more organized. tl;dr: Habitat (hab) is really neat. From the opscode folks.