From owner-freebsd-ports@freebsd.org Sun Oct 15 20:57:52 2017 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 0EBA1E4AC18 for ; Sun, 15 Oct 2017 20:57:52 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id E42B71612 for ; Sun, 15 Oct 2017 20:57:51 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id v9FKvoXV054645 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 15 Oct 2017 13:57:51 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Subject: Re: [ports]: GH_TAGNAME: how to figure out this tagname on downloadable archives? To: "O. Hartmann" Cc: FreeBSD Ports References: <20171015211940.44065925@thor.intern.walstatt.dynvpn.de> <19aa7f0a-3b52-5d34-cf80-136ef3fe489b@rawbw.com> <20171015214725.68e32dd9@thor.intern.walstatt.dynvpn.de> From: Yuri Message-ID: <130d6a72-ca4b-d948-68f6-69f8e7ac1f7e@rawbw.com> Date: Sun, 15 Oct 2017 13:57:49 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171015214725.68e32dd9@thor.intern.walstatt.dynvpn.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Oct 2017 20:57:52 -0000 On 10/15/17 12:47, O. Hartmann wrote: > all right, that is what I picked up from the porter's handbook, but I must have > overlooked the note (if there is anything like that) regarding the sufficient first 7 > digits. If you look at other ports, most use 7 digits. > I tried this earlier (yes, and I do also a make makesum ;-))), but I get a complete > different "structure" right now - no tarball which contains exactly OpenCL 2.1 or OpenCL > 2.2 (the one I'd like to download), but a complete hierarchie of the CL sources, starting > from OpenCL 1.0 to OpenCL 2.2. Either, there has been a change in the way OpenCL headers > are provided, or there is a magic trick to download, depending on the GH_TAGNAME, a > tarball ending in "*_GH0.tar.xz" The version downloaded using GH_TAGNAME should have the same structure as releases, unless the project structure itself has been radically changed between releases. The top folder name is going to be different for GH_TAGNAME. A release is just an alpa-numeric tag in a sequence of commits, nothing more. Yuri