On Wed, Jun 16, 2021 at 4:03 AM Peymaneh Nejad <[email protected]> wrote: > > Hi, > > I am working on packaging github.com/smallstep/zcrypto (which is a indirect > dependency of caddy) > > These are the dependencies: > > * github.com/smallstep/zcrypto depends on github.com/zmap/zcertificate > v0.0.0-20190521191901-30e388164f71 > > * github.com/zmap/zcertificate v0.0.0-20190521191901-30e388164f71 > > depends on github.com/zmap/zcrypto > > * github.com/zmap/zcrypto depends on github.com/zmap/zcertificate > v0.0.0-20180516150559-0e3d58b1bac4 > > So what I need to do is > 1. package the earlier commit of github.com/zmap/zcertificate which has no > dependencies > 2. build github.com/zmap/zcrypto using the older version > 3. build recent version of github.com/zmap/zcertificate > 4. build github.com/smallstep/zcrypto using the newer version > > I am wondering: Is it even possible to upload 2 Versions of the same exact > package to the same repos? Is there a debian way of solving this kind of > bootstrap problem? Advice is very appreciated :) >
You don't need to enable all features for a library. For example, in github.com/zmap/zcertificate, github.com/zmap/zcrypto is only imported in it's cmd and test. So just excluding these fearues, you can break the loop. -- Shengjing Zhu
