Best practice for mackaging software without "release tarballs"?

[Robert Backhaus]

On 19 May 2014 23:35, Lev Serebryakov <lev at freebsd.org> wrote:

> Hello, Ports.
>
>  I want to make port for TI MSP430 toolchain (binutils-newlib-gcc based,
> new
> one, not old and unsupported "devel/msp430*"), but problem is, that I need
> to package "tip of git branch", as all released tarballs (even snapshot
> ones) contains bugs.
>
>  What is the best practice for such situation? Is it possible to require
> git
> as build-dependency and checkout sources (with some fixed revision, of
> course, not "rolling" one) or should I prepare tarballs myself and put it
> into ${MASTER_SITE_LOCAL}?
>
> If the software has been ported, and the software is on Github, you can
specify any git tag and it will download that tag. For instance:

USE_GITHUB=     yes
GH_ACCOUNT=     bitcoin
GH_PROJECT=     bitcoin
GH_COMMIT=      4a102fa
GH_TAGNAME=     ${GH_COMMIT}

That said, most persons would prefer you pulled the latest release, and
applied necessary bug fixes as patches.