From owner-freebsd-ports@FreeBSD.ORG Mon May 19 13:47:28 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7523CB76 for ; Mon, 19 May 2014 13:47:28 +0000 (UTC) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3966A2DC1 for ; Mon, 19 May 2014 13:47:28 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:fc94:7754:4086:82d5]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 6E0364AC0C; Mon, 19 May 2014 17:47:26 +0400 (MSK) Date: Mon, 19 May 2014 17:47:23 +0400 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1466537923.20140519174723@serebryakov.spb.ru> To: Robert Backhaus Subject: Re: Best practice for mackaging software without "release tarballs"? In-Reply-To: References: <124848351.20140519173542@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 13:47:28 -0000 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