[ports]: GH_TAGNAME: how to figure out this tagname on downloadable archives?
ohartmann at walstatt.org
Sun Oct 15 19:47:48 UTC 2017
Am Sun, 15 Oct 2017 12:35:49 -0700
Yuri <yuri at rawbw.com> schrieb:
> On 10/15/17 12:19, O. Hartmann wrote:
> > Out of the blue there is a so called GH_TAGNAME. It reflects some late commit/revision
> > number on an archive. Now I try to figure out how to find such a GH_TAGNAME. Since I
> > do not push stuff to github, it is some new playfield and there might be an easy way
> > to figure out, but this way is obscured to me right now.
> GH_TAGNAME is the git commit hash, a hexadecimal number. github shows them for every
> commit. Usually, 7 first characters suffice. GH_TAGNAME overrides the port version when
> tarball is fetched. Just copy and paste it. :-)
Hello, thanks for your response,
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
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"
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 313 bytes
Desc: OpenPGP digital signature
More information about the freebsd-ports