conda-forge packaging difficulties #231
Description
Hello, I am working on packaging dydx v4 within the conda environment. I created several recipes for JS, C++ and Python clients.
However, conda recipes typically align with a release/tag from github and the only tag that I can follow is the v4-client-js@version, which leads to the recipe for python client having the same version ... which does not match the pypi package (v1.0.1)
Alternatively, I could directly use the pypi package, but we much prefer having our automation pick-up from your github repo directly
There was also a confusion as to the preferred naming convention, which I guess now is anchored on dydx-v4-client (I previously matched all v4-client, v4-client-py, dydxprotocol-v4-client), correct?
Thank you