I started with *your* rebar Portfile, updated the github config, descriptions and checksums, and added build.cmd and build.target... that's all.
Thus, you can even take over the maintenance if you want to ;-) G. On Mon, May 2, 2016 at 8:36 PM, MacPorts <[email protected]> wrote: > #51290: rebar3 Portfile submission > -------------------------+-------------------------------- > Reporter: jrjsmrtn@… | Owner: macports-tickets@… > Type: submission | Status: new > Priority: Normal | Milestone: > Component: ports | Version: > Resolution: | Keywords: > Port: rebar3 | > -------------------------+-------------------------------- > > Comment (by ciserlohn@…): > > I would prefer a separate port for rebar3. rebar2 and rebar3 are not > compatible but both in extensive use. It is much like the situation with > maven2/maven3/maven31. > > @jrjsmrtn<at>gmail.com: > If you don't mind if would opt-in as co-maintainer. > > -- > Ticket URL: <https://trac.macports.org/ticket/51290#comment:2> > MacPorts <https://www.macports.org/> > Ports system for OS X _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
