Best practice for mackaging software without "release tarballs"?

[Lev Serebryakov]

Hello, Robert.
You wrote 19 мая 2014 г., 17:40:39:

>>  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
RB> specify any git tag and it will download that tag. For instance:

RB> USE_GITHUB=     yes
RB> GH_ACCOUNT=     bitcoin
RB> GH_PROJECT=     bitcoin
RB> GH_COMMIT=      4a102fa
RB> GH_TAGNAME=     ${GH_COMMIT}
RB> That said, most persons would prefer you pulled the latest release, and
RB> applied necessary bug fixes as patches.
 Problem is, this is NOT a github :) git != github, you know?

-- 
// Black Lion AKA Lev Serebryakov <lev at FreeBSD.org>