Date: Mon, 19 May 2014 23:40:39 +1000 From: Robert Backhaus <robbak@robbak.com> To: lev@freebsd.org Cc: ports <ports@freebsd.org> Subject: Re: Best practice for mackaging software without "release tarballs"? Message-ID: <CABG_4jn3SLi-jCzE3zp9MZdKFXA=3sfexyEaPrpFZKBPd14XrQ@mail.gmail.com> In-Reply-To: <124848351.20140519173542@serebryakov.spb.ru> References: <124848351.20140519173542@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 May 2014 23:35, Lev Serebryakov <lev@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABG_4jn3SLi-jCzE3zp9MZdKFXA=3sfexyEaPrpFZKBPd14XrQ>