Date: Mon, 21 Dec 2015 13:36:35 -0500 From: Ricky G <ricky1252@hotmail.com> To: Chris H <bsd-lists@bsdforge.com>, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: RE: will the use of GitHub ever be fully explained? Message-ID: <SNT146-W3573A0CDDA2CEE0FF60958A1E40@phx.gbl> In-Reply-To: <8a8127da8d27494c17763acc506d23f2@ultimatedns.net> References: <8a8127da8d27494c17763acc506d23f2@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hey there Chris=2C
I actually invested some time figuring this out. When the GH_TAGNAME is us=
ed=2C that hash will be downloaded instead of the PORTVERSION. Pretty much =
the PORTVERSION variable is ignored other than the fact that is will be pac=
ked as ${PORTVERSION} so it is important to keep TAGNAME and PORTVERSION in=
sync.
> To: freebsd-ports@FreeBSD.org> From: bsd-lists@bsdforge.com
> Subject: will the use of GitHub ever be fully explained?
> Date: Mon=2C 21 Dec 2015 08:34:56 -0800
>=20
> Greetings fellow maintainers=2C
> 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=2C is concerned. Sure=2C 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?
>=20
> What I'd like to accomplish:
>=20
> PORTVERSION=3D 2.0
>=20
> USE_GITHUB=3D yes
>=20
> GH_TAGNAME=3D 95f841f
>=20
> But I don't think this will work.
>=20
> Thanks!
>=20
> --Chris
>=20
> --
>=20
>=20
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe=2C send any mail to "freebsd-ports-unsubscribe@freebsd.org=
"
=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SNT146-W3573A0CDDA2CEE0FF60958A1E40>