Date: Thu, 20 May 2021 12:01:20 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 254350] graphics/libepoxy: update to 1.5.7 Message-ID: <bug-254350-7141-7YV9YMXWXH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254350-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-254350-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254350 --- Comment #21 from John Hein <jcfyecrayz@liamekaens.com> --- (In reply to Evgeniy Khramtsov from comment #19) Daniel means (I think) that we could use MASTER_SITES=3Dhttps://github.com/anholt/libepoxy/releases/tag/${PORTVERSIO= N}/.=20 In this case, we _will_ need to change PORTVERSION to DISTVERSION. USE_GIT= HUB & GH_* can be removed, too. Why to use a release tarball (feel free to ignore this if you already understand why)... Upstream generated an actual release tarball (often by building some sort of 'dist' target). The release tarball can be different than just the tarball= of the tagged source. For instance, it may have pre-generated documentation f= iles so you don't have to pull in big documentation processing package dependenc= ies and run tools to build/install docs. That's one reason (of various other reasons) to prefer an actual release tarball. On the other hand, if a rele= ase tarball is gigantic and full of unnecessary / undesired pieces, one might prefer just the tarball of the tagged source. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254350-7141-7YV9YMXWXH>