From owner-freebsd-ports@freebsd.org Mon Dec 21 19:11:19 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E570FA4E359 for ; Mon, 21 Dec 2015 19:11:19 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C17ED1B40 for ; Mon, 21 Dec 2015 19:11:19 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id tBLJBM2J002378 for ; Mon, 21 Dec 2015 11:11:28 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: <8a8127da8d27494c17763acc506d23f2@ultimatedns.net>, From: "Chris H" Subject: Re: will the use of GitHub ever be fully explained? Date: Mon, 21 Dec 2015 11:11:28 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <8245fe8f7b4fb04f6b4b8ec54f53298b@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2015 19:11:20 -0000 On Mon, 21 Dec 2015 13:36:35 -0500 Ricky G wrote > Hey there Chris, > I actually invested some time figuring this out. When the GH_TAGNAME is > used, that hash will be downloaded instead of the PORTVERSION. Pretty much > the PORTVERSION variable is ignored other than the fact that is will be > packed as ${PORTVERSION} so it is important to keep TAGNAME and PORTVERSION > in sync. Big thanks for the thoughtful reply, Ricky! That's great to know! I just now managed to figure out a solution. My problem was that I *needed* the latest commit, but couldn't rely on the MASTER branch (for obvious reasons). So, even though it was "technically" 2.0, there was no 2.0 TAG. So I needed that specific COMMIT. So I ended up using the following: PORTVERSION= 2.0 DISTNAME= ${GH_ACCOUNT}-${GH_PROJECT}-${PORTVERSION}-${GH_COMMIT} USE_GITHUB= yes GH_ACCOUNT= yadda-yadda GH_PROJECT= project-name GH_COMMIT= 95f841f GH_TAGNAME= ${GH_COMMIT} Followed by a # make checksum to get all the missing bits -- and I was golden! :-) Thanks again, Ricky! > > Subject: will the use of GitHub ever be fully explained? > > Date: Mon, 21 Dec 2015 08:34:56 -0800 > > > > Greetings fellow maintainers, > > I'd like to update a port that's moved to GitHub. > > I pretty well understand the use MASTER_SITES where GitHub > > is concerned *except* where the need to use GIT_HASH for > > GH_TAGNAME, is concerned. Sure, I know how to put it there. > > But I am unclear how that affects the PORTVERSION entry. > > Does anyone have an example they'd be willing to share? > > Please? > > > > What I'd like to accomplish: > > > > PORTVERSION= 2.0 > > > > USE_GITHUB= yes > > > > GH_TAGNAME= 95f841f > > > > But I don't think this will work. > > --Chris --