Closed markspanbroek closed 3 years ago
Nimble is overly pedantic here.
Until this is solved https://github.com/nim-lang/nimble/issues/653 and nimble allows lockfiles https://github.com/nim-lang/nimble/issues/127 and we can move away from submodules there is no reason to try to solve this problem.
External users can install the library as well so it's non-blocking there.
Yes, it's indeed not blocking. But it's also annoying :) If I were to create a small PR to fix the warning, would you accept it?
When including secp256k1 as a dependency in nimble, I get the following warning: