[85132] trunk/dports/erlang

[Ryan Schmidt]

On Oct 9, 2011, at 22:31, bfulgham at macports.org wrote:

> Revision: 85132
>         http://trac.macports.org/changeset/85132
> Author:   bfulgham at macports.org
> Date:     2011-10-09 20:31:13 -0700 (Sun, 09 Oct 2011)
> Log Message:
> -----------
> Add rebar Erlang packaging tool.
> 
> Added Paths:
> -----------
>   trunk/dports/erlang/rebar/
>   trunk/dports/erlang/rebar/Portfile
> 
> Added: trunk/dports/erlang/rebar/Portfile
> ===================================================================
> --- trunk/dports/erlang/rebar/Portfile	                        (rev 0)
> +++ trunk/dports/erlang/rebar/Portfile	2011-10-10 03:31:13 UTC (rev 85132)
> @@ -0,0 +1,39 @@
> +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
> +# $Id: 
> +
> +PortSystem          1.0
> +
> +name                rebar
> +# no real version available
> +version             0.0.1
> +categories          devel
> +platforms           darwin
> +
> +maintainers         uwe-arzt.de:mail openmaintainer
> +
> +description         Rebar is an Erlang build tool that makes it easy to compile \
> +                    and test Erlang applications, port drivers and releases.
> +long_description    Rebar is a self-contained Erlang script, so it's easy to \
> +                    distribute or even embed directly in a project. Where possible, \
> +                    Rebar uses standard Erlang/OTP conventions for project \
> +                    structures, thus minimizing the amount of build configuration \
> +                    work. Rebar also provides dependency management, enabling \
> +                    application writers to easily re-use common libraries from a \
> +                    variety of locations (Git, Hg, etc).
> +                 
> +homepage            https://bitbucket.org/basho/rebar/wiki/Home
> +
> +fetch.type          hg
> +hg.url              https://bitbucket.org/basho/rebar
> +

You need to specify a version, tag, branch, revision, or similar specific entity to fetch from hg. Otherwise different users installing the port at different times will receive different versions of the software.

If upstream does not assign version numbers, then consider using a datestamp as the port's version field.