From owner-freebsd-ports@FreeBSD.ORG  Mon May 19 13:40:40 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 82589959;
 Mon, 19 May 2014 13:40:40 +0000 (UTC)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com
 [IPv6:2607:f8b0:4003:c02::22c])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 40E342CE8;
 Mon, 19 May 2014 13:40:40 +0000 (UTC)
Received: by mail-oa0-f44.google.com with SMTP id o6so6249523oag.31
 for <multiple recipients>; Mon, 19 May 2014 06:40:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=vqEb54ThT7UdmmaTBIOjedmfj8S0Z7vDPl9icgEXzdE=;
 b=h1/BcufjDpp+H9jTqAxoNG4WlXLY8XPmcibIs8jTV6wXpblbcekzWcn2SW3hrECFzZ
 Lswu38bM9NvuPtbwEt4ClcKHZ3cG97mPdhX2rDH99Iax5LgwKWQIbZZUKMBLuy5PmZKs
 6/54TmGJTdNIksdhi5ORaxohgfzfyCpg/i8lfjPbihnsPy0oed8XW+BxeyMtyTW1x4mU
 YebdXEzX2RbuqsZSG3Dmucu9lEC9ddV3T+7qwCxYCcN8miSjtJ3yjGGaAnqqh2+QzIPV
 qUIoxyvtQntkRwVtbLvOgUZt6i7Sundi5Q3S1R+0Vq0x47dGeOGfAUdtgz8CgWVpymOm
 hQPw==
MIME-Version: 1.0
X-Received: by 10.182.70.39 with SMTP id j7mr36422591obu.55.1400506839632;
 Mon, 19 May 2014 06:40:39 -0700 (PDT)
Sender: robbak@gmail.com
Received: by 10.76.0.111 with HTTP; Mon, 19 May 2014 06:40:39 -0700 (PDT)
In-Reply-To: <124848351.20140519173542@serebryakov.spb.ru>
References: <124848351.20140519173542@serebryakov.spb.ru>
Date: Mon, 19 May 2014 23:40:39 +1000
X-Google-Sender-Auth: Onuw6zKRYpxd8vNCm44w8sPfDfs
Message-ID: <CABG_4jn3SLi-jCzE3zp9MZdKFXA=3sfexyEaPrpFZKBPd14XrQ@mail.gmail.com>
Subject: Re: Best practice for mackaging software without "release tarballs"?
From: Robert Backhaus <robbak@robbak.com>
To: lev@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18
Cc: ports <ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 May 2014 13:40:40 -0000

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.