Suppose that I want to build my own set of psc-packages. How would I curate and verify a list of compatible libraries? It feels like this requires authors of package sets to confront the dependency problems that psc-package solves head-on?
Specifically, if I’m bringing in foolib-1.0, which depends on barlib-1.0, but then I want bazlib-1.0, and it depends on barlib-1.1 which is incompatible with foolib-1.0, I’m going to run into trouble.
Multiply this by 187 packages each with their own version (current count of curated packages in the psc-package set I’m using), and it seems like there’s a lot of DLL hell type complexity here.