It's hardly a "dependency hell" when it only affects developers, in what are essentially unique collision type situations, and are generally addressable by the

It's hardly a "dependency hell" when it only affects developers, in what are essentially unique collision type situations, and are generally addressable by the developer because the source is all present. And upstream maintainers of such intended-to-be-vendored code should generally be receptive to improving compatibility and build system configurability for such situations. And if they're not receptive/it's abandonware, congratulations your vendored library is now a fork and fix it yourself. When we refer to "dependency hell", AIUI, it's in reference to unresolvable runtime dependencies creating hell for end-users.