You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently at least one package (exprotobuf) which depends on gpb. Currently, the user must add a dependency record for gpb explicitly at the top-level, as hex dependencies don't get their own github dependencies fetched automatically.
It would be very convenient if gpb were published. More information on doing so can be found here: https://hex.pm/docs/publish
The text was updated successfully, but these errors were encountered:
@tomas-abrahamsson I'm more than willing to support the hex package for gpb if you'd like. Otherwise, you can find the info for publishing your lib to hex here, under "Publishing an Erlang package". Let me know what your preference is. Thanks!
Hi, thanks for the nudge to publish on hex.pm, for the pointers and for the offer to support it. I didn't know about this package repository before, so I've learned something new. I'll try to get publishing to hex.pm into my regular workflow for gpb.
I've just published gpb to hex.pm, I've not used Elixir much myself, so I haven't tested if the package works well or not (any feedback is welcome). I followed the code structure I found in a few other erlang packages on hex.pm.
There is currently at least one package (
exprotobuf
) which depends ongpb
. Currently, the user must add a dependency record forgpb
explicitly at the top-level, as hex dependencies don't get their own github dependencies fetched automatically.It would be very convenient if
gpb
were published. More information on doing so can be found here: https://hex.pm/docs/publishThe text was updated successfully, but these errors were encountered: