Closed Licenser closed 7 years ago
Thanks @Licenser... guessing you mean rebar3 :). @russelldb and I will discuss... still haven't made the move to rebar3 w/ this, but we should.
argh yes sorry rebar3 not riak3 ;) freudian slip there ...
So it doesn't need rebar3 to build or anything just as there is no hex upload option with anything else, that's all that requires rebar3 in it.
oh, slightly unrelated, I only listed myself as a co-maintainer in there so you don't get bothered by people having questions about the package. I'm not sure if the maintainers are the package maintainers or the code maintainers, just drop that if you take over the package :)
:+1: on moving to rebar3, please.
@Licenser of course, but as @cmeiklejohn pointed out... would be nice :). And, again, thank you :).
neva!
Ah well OK, but just because it's you russell ;)!
Yes since you don't have deps this is really all that's needed.
app.src
file needs a 'correct' version in it, last I checked the hex plugin doesn't handle git versioning.$ cat ~/.config/rebar3/rebar.config
{plugins, [rebar3_hex]}.
But other then that it'll just be rebar3 hex publish
and it sends it up.
Thanks @Licenser. When I get back to UK I'll do it. Promise! Thanks for your patience and help.
hey no worries at all, riak_dt helps me soooo much in my stuff it's really the least I can do.
+1
Hi I've published riak_dt as a hex package, this are the changes necessary to make it hex-able with riak3. Since it is your project it would be great if you'd take over the package, for that you can ask hex.pm to change ownership, until then I'll try to keep it up to date with the latest tagged release.