For me it depends on what I'm doing. - If building a one off system it really doesn't matter, so it's whatever happens to be easiest on the system I'm deployi

For me it depends on what I'm doing. - If building a one off system it really doesn't matter, so it's whatever happens to be easiest on the system I'm deploying it on. - If I'm adding software to a production system, especially one that will be exposed to the outside world then it's use the distro libraries - no if's or butts. The reason is straightforward: I _must_ get automatic security updates to all 3rd party software I install. I do not have the time to go through the 10's of thousands of CVE's released each year (that's 100 a day), then figure out what library it applies to, then track when they release an update. - The most constrained is when I am developing software I expect others I have never met will be using. E.g. stuff I release as open source. Then I target a range of libraries and interpreters, from those found on Debian stable (or even old-stable occasionally) to stuff installed by PIP. The reason is I expect people who are deploying to production systems (like me) will have little control over their environment: they must use whatever came with their distro.