I’m pretty sure there is no “otherwise simple” example, because depending on two versions of the same library isn’t usually something a project does deliberately (except as a last resort). It’s normally the consequence of an extremely complex forest of dependencies.
Andy > On Dec 5, 2019, at 5:52 PM, George Hartzell <hartz...@alerce.com> wrote: > > > Hi All, > > I'm working on improving the Spack (https://spack.io) package managers > support for Go-based application > (https://github.com/spack/spack/issues/13023). > > I'm trying to wrap my head around what Go's support for simultaneously > using multiple major versions of a dependency means to Spack. > > To that end, I'm looking for an otherwise simple application that uses > Go modules and depends on multiple versions of some library. I've > done a bit of searching but have come up dry. > > I'm wondering if any of you other nuts can point out examples? > > Thanks, > > g. > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/24041.46159.307729.108343%40alice.local. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/E809B0DE-82E7-4C0B-A3D0-572EB3FAA7FE%40gmail.com.
