Date: Mon, 19 May 2014 17:47:23 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Robert Backhaus <robbak@robbak.com> Cc: ports <ports@freebsd.org> Subject: Re: Best practice for mackaging software without "release tarballs"? Message-ID: <1466537923.20140519174723@serebryakov.spb.ru> In-Reply-To: <CABG_4jn3SLi-jCzE3zp9MZdKFXA=3sfexyEaPrpFZKBPd14XrQ@mail.gmail.com> References: <124848351.20140519173542@serebryakov.spb.ru> <CABG_4jn3SLi-jCzE3zp9MZdKFXA=3sfexyEaPrpFZKBPd14XrQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Robert.
You wrote 19 =D0=BC=D0=B0=D1=8F 2014 =D0=B3., 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 ne=
ed
>> 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=3D yes
RB> GH_ACCOUNT=3D bitcoin
RB> GH_PROJECT=3D bitcoin
RB> GH_COMMIT=3D 4a102fa
RB> GH_TAGNAME=3D ${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 !=3D github, you know?
--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1466537923.20140519174723>